Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sources DOT redhat DOT com
From: "Noel L Yap" <yap_noel AT jpmorgan DOT com>
To: cygwin AT sources DOT redhat DOT com
Message-ID: <85256921.0047DAC3.00@nyc-ntgw-n01.ny.jpmorgan.com>
Date: Wed, 19 Jul 2000 09:04:55 -0400
Subject: Re: Extending cygwin's process table
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline


cgf AT cygnus DOT com on 2000.07.18 23:43:19
>I'm also toying with trying to more closely tie cygwin pids to windows
>pids.

IMHO, this'd be great.

>Is anyone going to be bothered if pid creation is not monotonic?  By
>that I mean, parent pid 1000 may not create child pid 1001.  It may
>create child pid 27.

I don't think anything should be relying on this behaviour since it's not always
satisfied (ie when ppid is near the max pid allowed).

>It may still not be feasible to use cygwin pids as windows pids
>(possibly because I don't believe that pid 1 is special to windows) but
>I thought I'd give this a try anyway unless there is something that I'm
>missing.

Yeah, I'm not sure if it's possible, but it's worth a shot (unless someone out
there knows for sure that it's not possible).

Noel


This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com