Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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: Tue, 3 Feb 2004 13:38:20 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Re Re: Is there a translation from windows events to cygwin signals ?
Message-ID: <20040203183820.GD3696@redhat.com>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <C2F0FC2A5C4B3E44ADF4327E699486A50A0EEE AT mail2 DOT de DOT thorlabs DOT local> <Pine DOT GSO DOT 4 DOT 56 DOT 0402031238070 DOT 24268 AT slinky DOT cs DOT nyu DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.56.0402031238070.24268@slinky.cs.nyu.edu>
User-Agent: Mutt/1.4.1i
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

On Tue, Feb 03, 2004 at 12:44:32PM -0500, Igor Pechtchanski wrote:
>FWIW, Cygwin's kill() understands Win32 PIDs, so you can at least skip
>step 3.  I suggest looking at Cygwin's implementation of /bin/kill (in CVS
>as winsup/utils/kill.cc).

Sorry to contradict you again, Igor, but cygwin's kill understands win32
pids only insofar as the win32 pid corresponds to a cygwin pid.  You
can't use cygwin's kill() to kill a pure win32 process.  It only works
on cygwin processes.  In particular, if a process has been exec()ed its
cygwin pid will be that of the original process but its actual windows
pid will be different.

The kill.exe program has special logic for killing non-cygwin pids when
-f is specified.  This is not supported by the cygwin DLL, however.

cgf

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