Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com From: Chris Faylor Date: Wed, 19 Jul 2000 14:21:38 -0400 To: cygwin@sources.redhat.com Subject: Re: Extending cygwin's process table Message-ID: <20000719142137.G17938@cygnus.com> Reply-To: cygwin@sources.redhat.com Mail-Followup-To: cygwin@sources.redhat.com References: <85256921.0047DAC3.00@nyc-ntgw-n01.ny.jpmorgan.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <85256921.0047DAC3.00@nyc-ntgw-n01.ny.jpmorgan.com>; from yap_noel@jpmorgan.com on Wed, Jul 19, 2000 at 09:04:55AM -0400 On Wed, Jul 19, 2000 at 09:04:55AM -0400, Noel L Yap wrote: >cgf@cygnus.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). Yeah, I certainly know this. I was just wondering if people would be shocked and outraged by any new "random" behavior. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com