X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Message-ID: <4B0AAA47.6050507@etr-usa.com>
Date: Mon, 23 Nov 2009 08:29:11 -0700
From: Warren Young <warren AT etr-usa DOT com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Cygwin-L <cygwin AT cygwin DOT com>
Subject: Re: [1.7] Updated: cygwin-1.7.0-65
References: <20091119094439 DOT GC29173 AT calimero DOT vinschen DOT de> 	 <20091120093210 DOT GQ29173 AT calimero DOT vinschen DOT de> 	 <f4d6f44b0911202003j71954bf0lf5b6696acdfe7e7d AT mail DOT gmail DOT com> 	 <20091121110204 DOT GB23273 AT calimero DOT vinschen DOT de> 	 <f4d6f44b0911210743r221b5107qfa4ebee00c9a97e9 AT mail DOT gmail DOT com> 	 <20091121212239 DOT GD29173 AT calimero DOT vinschen DOT de> 	 <f4d6f44b0911211733t15929d5ctac8e06c977bbc10c AT mail DOT gmail DOT com> 	 <20091123091612 DOT GE29173 AT calimero DOT vinschen DOT de> 	 <f4d6f44b0911230143k6437ea31n4a7788fdeef8393b AT mail DOT gmail DOT com> 	 <20091123100122 DOT GI29173 AT calimero DOT vinschen DOT de> <f4d6f44b0911230607h4d1b76c3x5bc478aecccf7 AT mail DOT gmail DOT com>
In-Reply-To: <f4d6f44b0911230607h4d1b76c3x5bc478aecccf7@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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

Huang Bambo wrote:
>> The leak is a result of the parent process not calling wait(2) or
>> waitpid(2) to reap the child process.  
> 
> There's some diffirence between cygwin and other *nix:
> In other *nix with this condition, those ended child process could be
> list by ps command with <defunc>tag

How much sense does it make to talk about zombies in the Cygwin world? 
As soon as the last Cygwin-using process dies, all these resources are 
freed up, right?  Oppose a standalone POSIX kernel, where orphaned 
processes get reparented to init(8), which never dies until reboot, and 
the kernel can't be restarted without rebooting the whole machine.  On 
such a system, zombies are all but unkillable, not like on Cygwin.

Maybe we need another designation.  I suggest "undead skeleton".  Easier 
to kill, especially if you have a mace enchanted with shock damage.

> will you fix it?

PTC, I'm sure.

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