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
Message-Id: <200207170245.g6H2jGO28572@d-ip-129-15-78-125.cs.ou.edu>
X-Authentication-Warning: d-ip-129-15-78-125.cs.ou.edu: jcast owned process doing -bs
To: cygwin AT cygwin DOT com
Subject: Re: Broken since 1.3.10, or earlier
In-Reply-To: Message from Christopher Faylor <cgf@redhat.com>
   of "Tue, 16 Jul 2002 22:27:43 EDT." <20020717022743 DOT GA24046 AT redhat DOT com>
Date: Tue, 16 Jul 2002 21:45:16 -0500
From: Jon Cast <jcast AT ou DOT edu>

Christopher Faylor <cgf AT redhat DOT com> wrote:
<snip>
> bash makes assumptions that pids grow monotonically but that is not
> the case on windows.  It's possible that you can run a program twice
> and get the same pid twice in a row -- especially on Windows 9x.  I
> try to work around this in cygwin by keeping a certain number of
> process handles open, so that the pids won't be reused, but that
> still causes problems when you are fork/execing processes quickly.

Just out of curiosity, why would bash care if pids grow monotonically?
(I know I can check the sources, but I'm lazy.)

Jon Cast


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/