Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <428627E7.2080609@x-ray.at>
Date: Sat, 14 May 2005 18:31:35 +0200
From: Reini Urban <rurban@x-ray.at>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.8b) Gecko/20050217
MIME-Version: 1.0
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
CC: Sonam Chauhan <sonam.chauhan@ce.com.au>
Subject: Re: problems in Perl process management
References: <55E0A3E94323974F83CFC5AAB96F68B8014190EB@snnexc03.in.ce.com.au>
In-Reply-To: <55E0A3E94323974F83CFC5AAB96F68B8014190EB@snnexc03.in.ce.com.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Sonam Chauhan schrieb:
>>I had thought Gerrit would release a new 5.8.6 with them, but this
>>doesn't seem to have happened; don't know if I somehow dropped the
>>ball on that.  In any case, I'm really really hoping that 5.8.7 is
>>released in the next few weeks.
>>
>>I don't know anything about problems with Proc::ProcessTable other than
>>what may have been mentioned in that thread.  Perhaps you'd like to look
>>into it further?
> 
> Yes. 
> 
> Can you confirm whether your patch addresses a problem Reini reported your
> thread in Feb? It was this message: 
> 	http://sourceware.org/ml/cygwin/2005-02/msg00224.html 
> ...where Reini said:
> 
>>>But the cygwin pid's seem to be wrong.
>>>Some cygwin processes are not detected as such, so the pids are 
>>>listed as winpid's. And fname is printed as windows path for 
>>>those processes, though it should be printed as cygwin path. 
>>>I'll complain upstream.

Sorry for being late. I'm catching up old email.

I didn't complain yet upstream at rt.cpan.org because I wanted to wait 
for our 5.8.7 release. But you can do it by yourself also, or fix it in 
this module XS. It's really easy with the cygwin provided translation 
functions.
   See http://sourceware.org/ml/cygwin/2005-02/msg00154.html

> My problem is similar - in Cygwin, Proc::ProcessTable reports some PIDs as
> WINPIDs instead of Cygwin PIDs.
> 
> In terms of my testcase (attached to my first email), the effect is that the
> get_pids method in Proc::Killfam.pm does not recurse down all descendant
> processes due to inaccurate PID reporting by Proc::ProcessTable.

-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/
http://phpwiki.org/

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/