Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com From: Chris Faylor Date: Wed, 19 Jul 2000 10:46:18 -0400 To: cygwin-developers AT sources DOT redhat DOT com Subject: Re: Extending cygwin's process table Message-ID: <20000719104618.B17347@cygnus.com> Reply-To: cygwin-developers AT sources DOT redhat DOT com Mail-Followup-To: cygwin-developers AT sources DOT redhat DOT com References: <20000718234319 DOT A16333 AT cygnus DOT com> <200007191231 DOT IAA23425 AT envy DOT delorie DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007191231.IAA23425@envy.delorie.com>; from dj@delorie.com on Wed, Jul 19, 2000 at 08:31:34AM -0400 On Wed, Jul 19, 2000 at 08:31:34AM -0400, DJ Delorie wrote: >> It may still not be feasible to use cygwin pids as windows pids > >This isn't possible because unix preserves pids across exec() but >Windows doesn't. If you can fix *that* problem, then maybe... Yeah, I am well aware of the problem but I have an idea... cgf