Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <55E0A3E94323974F83CFC5AAB96F68B8014192F1@snnexc03.in.ce.com.au>
From: Sonam Chauhan <sonam DOT chauhan AT ce DOT com DOT au>
To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: RE: problems in Perl process management
Date: Mon, 16 May 2005 15:54:19 +1000
MIME-Version: 1.0
Content-Type: text/plain
X-IsSubscribed: yes

Reini - Thanks for replying man.

> 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, 

OK, I'm not that talented, so I didn't try fixing this bug, but I did report
it with a better testcase here:
	http://rt.cpan.org/NoAuth/Bug.html?id=12840

> 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

I had a look at your post, but out of curiosity, isn't it about adding
functionality for looking up the WINPID from the Cygwin process ID? Is the
fix really that simple? After all, Proc::ProcessTable misreports the PID and
PPID only under certain conditions -- this would indicate a complex issue in
Proc::ProcessTable XS code, right?

Regards,
Sonam Chauhan
-- 
Electronic Commerce, Corporate Express Australia Ltd.
Phone: +61-2-9335-0725, Email: sonam DOT chauhan AT ce DOT com DOT au
 

> -----Original Message-----
> From: Reini Urban [mailto:rurban AT x-ray DOT at]
> Sent: Sunday, 15 May 2005 2:32 AM
> To: 'cygwin AT cygwin DOT com'
> Cc: Sonam Chauhan
> Subject: Re: problems in Perl process management
> 
> 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/