Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
From:	Chris Faylor <cgf AT cygnus DOT com>
Date:	Tue, 18 Jul 2000 23:43:19 -0400
To:	cygwin AT sourceware DOT cygnus DOT com
Subject:	Extending cygwin's process table
Message-ID:	<20000718234319.A16333@cygnus.com>
Reply-To:	cygwin AT sources DOT redhat DOT com
Mail-Followup-To:	cygwin AT sourceware DOT cygnus DOT com
Mime-Version:	1.0
User-Agent:	Mutt/1.2i

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 AT sourceware DOT cygnus DOT com

- Raw text -