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 Message-ID: <4272C2F7.9030905@agilent.com> Date: Fri, 29 Apr 2005 16:27:51 -0700 From: Earl Chew User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Help understanding process tree References: <4270F2F5 DOT 5010000 AT agilent DOT com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 29 Apr 2005 23:27:54.0042 (UTC) FILETIME=[1154E1A0:01C54D13] Earl Chew wrote: > I'd like help understanding why Process Explorer shows cygwin > child processes as orphans, but win32 child processes as children. > > How is this so? I think I've discovered the reason for this is that during the fork/exec, the child that does the exec is discarded and replaced with a new process that executes the new application. Earl -- 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/