Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Fri, 29 Apr 2005 10:12:10 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Help understanding process tree Message-ID: <20050429081210.GL2572@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <4270F2F5.5010000@agilent.com> <20050428150258.GB13295@trixie.casa.cgf.cx> <20050429072631.GC3112@efn.org> <4271E5C6.876A373D@dessent.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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@cygwin.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/