Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: "Tony Arnold" To: Subject: RE: Extending cygwin's process table Date: Wed, 19 Jul 2000 16:16:01 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-reply-to: <20000719105042.D17347@cygnus.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Chris, > >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... OK. Just a suggestion that I think could prove very useful. > 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. I guess if you were going to implement my suggestion above, then there would be a requirement for cygwin PIDs and Windows PIDs to be unique accross the system, i.e., you could not have cygwin PID be the same number as a Windows PID. Regards, Tony. -- Tony Arnold, Head of Science and Engineering Support Unit, University of Manchester. Tel: +44 161 275 6093, Fax: +44 161 275 6071 E-mail: tony DOT arnold AT man DOT ac DOT uk, Home: http://www.man.ac.uk/Tony.Arnold -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com