Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Fri, 29 Apr 2005 10:12:10 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Help understanding process tree
Message-ID:	<20050429081210.GL2572@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<4270F2F5 DOT 5010000 AT agilent DOT com> <20050428150258 DOT GB13295 AT trixie DOT casa DOT cgf DOT cx> <20050429072631 DOT GC3112 AT efn DOT org> <4271E5C6 DOT 876A373D AT dessent DOT net>
Mime-Version:	1.0
In-Reply-To:	<4271E5C6.876A373D@dessent.net>
User-Agent:	Mutt/1.4.2i

On Apr 29 00:44, Brian Dessent wrote:
> To the original poster... Try "procps aux --forest" if you want an
> accurate picture of the Cygwin process tree, since procps is a Cygwin
> program and thus will use Cygwin PIDs.

pstree from the psmisc package prints nice process trees as well (as the
name suggests).


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -