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 Date: Wed, 23 Apr 2003 17:18:35 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: CVS head bash problem Message-ID: <20030423211835.GE9303@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20030423015402.GB38081907@hpn5170x> <3.0.5.32.20030423000357.007f9780@incoming.verizon.net> <20030423193236.GC8396@redhat.com> <20030423210354.GF11137@cygbert.vinschen.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/