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/