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 X-Authentication-Warning: localhost.localdomain: ronald owned process doing -bs Date: Tue, 15 Jul 2003 10:22:26 +0200 (CEST) From: Ronald Landheer-Cieslak X-X-Sender: ronald@localhost.localdomain To: cygwin@cygwin.com Subject: Re: cygwin 1.5.0-1 forked off child processes have open handles to non-existant processes In-Reply-To: <20030710173752.GB6345@redhat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII OK, I see Thanx :) rlc On Thu, 10 Jul 2003, Christopher Faylor wrote: > On Thu, Jul 10, 2003 at 05:48:21PM +0200, Ronald Landheer-Cieslak wrote: > >I was just walking my process tree with the process explorer when I saw > >the cron process had an open handle to a non-existant process > >(presumably its parent). > > That is correct. It is working as designed. It has always done this. > It keeps a handle open to the process so that the pid of the original > process will not be reused. It also keeps several process handles open > so that pids will not be reused too quickly as that confuses bash. > > 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/ > -- 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/