Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Wed, 23 Apr 2003 17:18:35 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: CVS head bash problem
Message-ID: <20030423211835.GE9303@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <b84vjb$sqd$1 AT main DOT gmane DOT org> <b84q3m$drl$1 AT main DOT gmane DOT org> <20030423015402 DOT GB38081907 AT hpn5170x> <b84upp$qb5$1 AT main DOT gmane DOT org> <b84vjb$sqd$1 AT main DOT gmane DOT org> <3 DOT 0 DOT 5 DOT 32 DOT 20030423000357 DOT 007f9780 AT incoming DOT verizon DOT net> <20030423193236 DOT GC8396 AT redhat DOT com> <20030423210354 DOT GF11137 AT cygbert DOT vinschen DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030423210354.GF11137@cygbert.vinschen.de>
User-Agent: Mutt/1.4.1i

On Wed, Apr 23, 2003 at 11:03:54PM +0200, Corinna Vinschen wrote:
>On Wed, Apr 23, 2003 at 03:32:36PM -0400, Christopher Faylor wrote:
>> It just occurred to me that this is probably the old bash "reuse the
>> pid" problem.  Bash is confused when pid numbers are reused in quick
>> succession, which can be the case on Windows.  I thought that Corinna
>> had turned on something in bash to work around this problem.  I wonder
>> if it is no longer on in recent versions of bash or if the workaround
>> doesn't work.
>
>It's still in use in the current bash version 2.05b.  It's a configure
>thingy which activates this for LynxOS and Cygwin.  I didn't switch it
>off.

The problem still feels like this one, though.  I wonder if the bash
option which controls this is just not perfect and still requires
cygwin's workaround.  That's too bad, if so.  I always hated keeping
the process handles open in fork.cc.

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/