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:	Wed, 19 Jul 2000 01:36:54 -0400
To:	cygwin AT sources DOT redhat DOT com
Subject:	Re: Extending cygwin's process table
Message-ID:	<20000719013654.A16526@cygnus.com>
Reply-To:	cygwin AT sources DOT redhat DOT com
Mail-Followup-To:	cygwin AT sources DOT redhat DOT com
References:	<8600BF007197944F8DD3906E40CB42808FCE AT itdomain001 DOT itdomain DOT net DOT au>
Mime-Version:	1.0
User-Agent:	Mutt/1.2i
In-Reply-To:	<8600BF007197944F8DD3906E40CB42808FCE@itdomain001.itdomain.net.au>; from robert.collins@itdomain.com.au on Wed, Jul 19, 2000 at 03:30:10PM +1000

On Wed, Jul 19, 2000 at 03:30:10PM +1000, Robert Collins wrote:
>	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.

Yes.  The start time is stored now and I would not remove this.  I could
add an option to ps to sort the processes by start time, too.

I didn't make it clear that the reason that the pids would look like this
is that Windows is very random in its pid assignment.

cgf

>-----Original Message-----
>From: Chris Faylor [mailto:cgf AT cygnus DOT com]
>Sent: Wednesday, 19 July 2000 1:43 PM
>To: cygwin AT sourceware DOT cygnus DOT 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 AT sourceware DOT cygnus DOT com
>
>
>--
>Want to unsubscribe from this list?
>Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

-- 
cgf AT cygnus DOT com                        Cygnus Solutions, a Red Hat company
http://sourceware.cygnus.com/         http://www.redhat.com/

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

- Raw text -