This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Help understanding process tree
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 28 Apr 2005 11:02:58 -0400
- Subject: Re: Help understanding process tree
- References: <4270F2F5.5010000@agilent.com>
- Reply-to: cygwin at cygwin dot com
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/