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: Fri, 17 Sep 2004 11:04:59 -0400 From: "Pierre A. Humblet" To: cygwin AT cygwin DOT com Subject: Re: Bash returns incorrect process status Message-ID: <20040917150459.GA155849@Worldnet> References: <753F1E41ACB9D51190C00090277218D80171EE39 AT WWMESSD206> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <753F1E41ACB9D51190C00090277218D80171EE39@WWMESSD206> User-Agent: Mutt/1.4.1i On Fri, Sep 17, 2004 at 02:47:57PM +0100, Dolton Tony AB wrote: > (Sorry if this doesn't appear in the right place - I'm still unable to > subscribe to the list and had to bodge a reply.) > > I would just like to say that the patch specified in > http://cygwin.com/ml/cygwin/2004-09/msg00783.html fixes the problem that I > reported in http://cygwin.com/ml/cygwin/2004-09/msg00401.html. Obviously, it > wasn't simply the exiting of the background processes that was the problem, > it was the reuse of pids as well. Do you see the patch kicking in, the "Found old pid..." message on stderr? > Given the caveats attached to the patch, I'm hoping that a "proper" version > will eventually be issued in a new release of bash. Will this be the case? > I've noticed that bash doesn't get issued too often. There is more to the story, see http://cygwin.com/ml/cygwin/2004-09/msg00812.html Also it's not surprising that the current snapshot doesn't fully fix the problem http://cygwin.com/ml/cygwin/2004-09/msg00813.html , increasing the pid reuse period only reduces the likelihood that the problem shows up. Pierre -- 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/