Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Thu, 28 Apr 2005 11:02:58 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Help understanding process tree Message-ID: <20050428150258.GB13295@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <4270F2F5 DOT 5010000 AT agilent DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4270F2F5.5010000@agilent.com> User-Agent: Mutt/1.5.8i On Thu, Apr 28, 2005 at 07:28:05AM -0700, Earl Chew wrote: >I'm working on a cygwin problem and have been looking at the Win32 >process tree structure using Process Explorer from Sysinternals: > >http://www.sysinternals.com/ntw2k/freeware/procexp.shtml > >I'd like help understanding why Process Explorer shows cygwin >child processes as orphans, but win32 child processes as children. > >How is this so? > >For example, if I start bash, then start cmd /c dir, I will see: > >bash > bash > cmd /c dir > >My reading of the code is that the 2nd bash is the fork-stub that is >waiting for cmd to complete. > >Now, if I start sleep 30, I will see: > >bash >sleep 30 Right. cmd is a non-cygwin program so it needs a cygwin stub to handle being "execed". sleep is a cygwin program and does not require any hand holding. cgf -- 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/