Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Subject: RE: Extending cygwin's process table
Date: Wed, 19 Jul 2000 15:30:10 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Message-ID: <8600BF007197944F8DD3906E40CB42808FCE@itdomain001.itdomain.net.au>
content-class: urn:content-classes:message
Thread-Topic: Extending cygwin's process table
Thread-Index: Ab/xM31laP90Wyb7SWmsEu88DgfX/QADsANA
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: <cygwin@sources.redhat.com>
Content-Transfer-Encoding: 8bit

Chris,
	sounds good, If ps can give the start time for a process then it
won't cause any grief for me. If there is no way for me to tell the
order processes are launched in though, that could be difficult.

Rob

-----Original Message-----
From: Chris Faylor [mailto:cgf@cygnus.com]
Sent: Wednesday, 19 July 2000 1:43 PM
To: cygwin@sourceware.cygnus.com
Subject: Extending cygwin's process table


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.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com