This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
Re: Extending cygwin's process table
- To: cygwin at sources dot redhat dot com
- Subject: Re: Extending cygwin's process table
- From: Andre Bleau <andre dot bleau at courriel dot polymtl dot ca>
- Date: Wed, 19 Jul 2000 09:45:54 -0400
>I am planning on revamping cygwin's process table for version 1.1.4.
>I hope to make process creation a little faster and to also allow many
>more cygwin processes.
>
>I'm also toying with trying to more closely tie cygwin pids to windows
>pids.
>
>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.
>
>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.
In other UNIXes that I know (IRIX, Solaris), there is no garantee of pid
ordering among parent and child process. If parent forks several children
that fork too asynchronously, then I don't see any way of getting monotonic
ordering.
I think that any program that would rely on monotonic pids would be
intrinsically unstable and should be fixed instead.
Functions that map PIDs between Windows and Cygwin would be useful; e.g.,
getWindowsPID(CygwinPID) and getCygwinPID(WindowsPID).
André Bleau, ing., analyste
email: bleau at courriel dot polymtl dot ca
(Fight SPAM: encode your email-address)
Département de génie électrique et Electric Engineering and
de génie informatique Computer Engineering department
École Polytechnique de Montréal Montreal Polytechnic School
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com