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 10:50:42 -0400 To: cygwin@sources.redhat.com Subject: Re: Extending cygwin's process table Message-ID: <20000719105042.D17347@cygnus.com> Reply-To: cygwin@sources.redhat.com Mail-Followup-To: cygwin@sources.redhat.com References: <20000718234319.A16333@cygnus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from tony.arnold@man.ac.uk on Wed, Jul 19, 2000 at 02:27:26PM +0100 On Wed, Jul 19, 2000 at 02:27:26PM +0100, Tony Arnold wrote: >> 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. > >Does this mean we could get ps to report the Windows processes as well as >the cygwin ones? Also for kill to work on Windows processes as well as >cygwin ones, or is this asking too much? Nope. I was going to investigate doing this, too. I've had generic pid walking code for a couple of years that I was going to "round tuit" into cygwin but... Btw, I should point out that it's not likely that I can get a 100% correspondence between windows pids and cygwin pids. Instead, the pids will have a likelihood of being the same but no guarantee. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com