X-Recipient: archive-cygwin AT delorie DOT com
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:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=oRDD9EAxXjzuP6kIdL7/L6oVbUiS7
	LGjSdTOayuqYrR2sN8PGmslp0jbRIIVj1kVvt2UhTp7Vz7XE0md2D1bhKNeppeXr
	d4XdFVmv1/V/F4odYb7XRaLSCyn32OSkn7Er0jhNVAnUnMaIh4jzO6dHu2c3713G
	IZmJoVxNbxai8M=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; s=default; bh=EB3QyYgQjV6bg0DAwROlxFw7LZM=; b=oDm
	K9GkYVwUFrtPGMP8AXrQh0FDe8xVEC6FDEan9R4niJ9u3owQ+wXVlv8oZchKwZ0o
	rM9eSKAYmYmyAO3vQrkzHrIVtnNc1VBDYTuDMIAJeaseaqUiWRzjgGJfRi8sXk4f
	EBNo6LiESufu2OwcwSor8O6YQ8mo46ssiKEvPZGI=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2
X-HELO: nihxway2out.hub.nih.gov
X-IronPortListener: Outbound_SMTP
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIGACEAcFKcKEew/2dsb2JhbABZgweBDL80gSwWbQeCJQEBAQMBEihECwIBCA0VFBAfExcBDQEBBBsah18GnTycf48WOIMfgQ0DjlOQGoslgyaCKg
From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr AT ncbi DOT nlm DOT nih DOT gov>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: RE: SIGKILL and TerminateProcess
Date: Tue, 29 Oct 2013 18:37:46 +0000
Message-ID: <5F8AAC04F9616747BC4CC0E803D5907D0C40B0C6@MLBXv04.nih.gov>
References: <5F8AAC04F9616747BC4CC0E803D5907D0C40AFEB AT MLBXv04 DOT nih DOT gov> <20131029172205 DOT GA1433 AT ednor DOT casa DOT cgf DOT cx>
In-Reply-To: <20131029172205.GA1433@ednor.casa.cgf.cx>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id r9TIc43u010694

> Sorry but we aren't going to redesign the signal delivery mechanism for
> your use case.

It wasn't exactly a redesign I was asking about;  rather an addition
(or an improvement, if you will) for only the case of that one KILL
signal, which is already a special thing in all aspects even on UNIX.

> Cygwin does not guarantee delivery of signals to processes which are
> calling Windows API functions directly.  If you do that you should be
> prepared to deal with problems.

Windows Sleep() was just a convenient dummy to demonstrate how SIGKILL does
not kill.  CYGWIN lets me access some Windows-specific APIs (the same way one
would do by using some UNIX-flavor-specific libraries), without having to port them
all to CYGWIN first.  Such code becomes a real problem in pipelining because
it cannot be reliably managed from other processes (which would all require
modifications to do TerminateProcess tricks throughout; or use the special
CYGWIN command-like utility) where just kill(9) would have been sufficient..

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