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
Date: Fri, 13 May 2005 05:43:37 -0700
From: Yitzchak Scott-Thoennes <sthoenna AT efn DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: problems in Perl process management
Message-ID: <20050513124337.GA2664@efn.org>
References: <55E0A3E94323974F83CFC5AAB96F68B8014190EB AT snnexc03 DOT in DOT ce DOT com DOT au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <55E0A3E94323974F83CFC5AAB96F68B8014190EB@snnexc03.in.ce.com.au>
User-Agent: Mutt/1.4.1i
X-IsSubscribed: yes

On Fri, May 13, 2005 at 07:11:23PM +1000, Sonam Chauhan wrote:
> 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.
> 
> My problem is similar - in Cygwin, Proc::ProcessTable reports some PIDs as
> WINPIDs instead of Cygwin PIDs.

No, my patch does nothing for Proc::ProcessTable; it just provides access
to the pid conversion functions from perl.

> 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.
> 
> > > > ActiveState perl is a windows program.  You can't send cygwin (aka
> > unix)
> > > > signals to a windows proram.
> > > This should be possible if the ActiPerl Windows executable was executed
> > from
> > > a Cygwin terminal -- 'ps' shows it running and 'kill -9' should kill it.
> > 
> > ? "This should be possible" meaning what?  You indeed can't send cygwin
> > signals (which AIUIkill -9 is not) to windows programs.
> 
> What is 'AIUIkill'? Did you mean 'kill -9'? Isn't SIGKILL a Unix signal? The
> context of the original discussion was about killing processes by sending a
> SIGKILL (please see: http://sourceware.org/ml/cygwin/2005-05/msg00550.html )

There was supposed to be a space after AIUI (as I understand it).
As I understand it, kill -9 does not send a signal, and certainly not to a
windows program.

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