DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:content-type
	:content-transfer-encoding:mime-version; q=dns; s=default; b=BGw
	kArvxM00zdg6yXhoDnZQ9gKLod2uGq97P1z4OJZCcPawNMyXnLvzgDAZUKInF+IX
	NVA3kNitxoikb4i33K+jkQMY+pPjHBdiFxk3syMhuwcEKfdE1jBXYm4vyHA6bzyd
	oZPb7r1WMPtlZFYZurRhq9pswQV550XiIH0plBqU=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: SIGKILL and TerminateProcess
Date: Tue, 29 Oct 2013 15:47:47 +0000
Message-ID: <5F8AAC04F9616747BC4CC0E803D5907D0C40AFEB@MLBXv04.nih.gov>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

Hello List,

I have a question, as to why CYGWIN does not use the TerminateProcess approach when
dealing with SIGKILL sent to a process (in the manner the CYGWIN's own kill utility
does when invoked with -f)?  Usually SIGKILL is expected to reliably terminate
its victim (let alone it can't be intercepted, hence, does not need any "handling"
provisions).  Yet under CYGWIN, if the point of execution is found as "unsafe" in the
target process, the signal cannot be delivered quickly.  Such as when the process is busy dealing with a time-consuming Windows API (the dumbest example is Sleep() ;-),
then the process will not get killed even with SIGKILL.  Could CYGWIN please consider
special-casing SIGKILL to perform something similar to the force-killing of the
command-line utility?

Thanks,

Anton Lavrentiev
Contractor NIH/NLM/NCBI


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