From: Jon Cast <jcast@ou.edu>
To: cygwin@cygwin.com
Subject: Re: Broken since 1.3.10, or earlier
Date: Tue, 16 Jul 2002 20:38:00 -0000 [thread overview]
Message-ID: <200207170245.g6H2jGO28572@d-ip-129-15-78-125.cs.ou.edu> (raw)
In-Reply-To: Message from Christopher Faylor <cgf@redhat.com> of "Tue, 16 Jul 2002 22:27:43 EDT." <20020717022743.GA24046@redhat.com>
Christopher Faylor <cgf@redhat.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/
next prev parent reply other threads:[~2002-07-17 2:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-16 18:15 Dan Higgins
2002-07-16 18:23 ` Randall R Schulz
2002-07-16 18:30 ` Dan Higgins
2002-07-16 18:39 ` Dan Higgins
2002-07-16 20:12 ` Christopher Faylor
2002-07-16 20:38 ` Jon Cast [this message]
2002-07-16 21:02 ` Christopher Faylor
2002-07-16 22:16 ` Jon Cast
2002-07-17 5:47 ` egor duda
2002-07-17 6:57 ` Christopher Faylor
2002-07-16 18:32 ` Dario Alcocer
2002-07-16 23:17 ` Andrew DeFaria
2002-07-17 12:31 ` Dan Higgins
2002-07-17 12:52 ` Bernard A Badger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200207170245.g6H2jGO28572@d-ip-129-15-78-125.cs.ou.edu \
--to=jcast@ou.edu \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).