delorie.com/archives/browse.cgi | search |
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:date:from:to:subject:message-id:reply-to | |
:references:mime-version:content-type:in-reply-to; q=dns; s= | |
default; b=dzfc05VegvgztDgM6Kje3ZacbBLfdrblr4PZEuO3gUuQhYpNxPZGY | |
27yCSZmjtK4KrcmkRPX0fWSQzzKxcRkuw8UdB4hCeqZkUgEHSWuofhPFJaYc6Zuz | |
JzOZ4uWOmG7H9kS0PqVDB7FvisxDsdUrAFLHgoh+xzuGsfjkRbmNgc= | |
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:date:from:to:subject:message-id:reply-to | |
:references:mime-version:content-type:in-reply-to; s=default; | |
bh=EK0wCJnrzBxJ9W1bDGoR4WbcSQg=; b=cEcgRv3IUrh1s0gGIAayQJW4RUlj | |
hMB3WXtMz5o5YV65B+YS6AMINnO75D/aC17bvzt9MIhdBvjf1bxlHxcWof/YG+7v | |
yDI12K+pDlbJl0YqCin5AZ+7WXgPP1249d5OUtz4RC2aFt+sT57USf6A5mUWc2HQ | |
ygOzHDyWfti3F0A= | |
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=-0.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 |
X-HELO: | mho-02-ewr.mailhop.org |
X-Mail-Handler: | Dyn Standard SMTP by Dyn |
X-Report-Abuse-To: | abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) |
X-MHO-User: | U2FsdGVkX1+k2urR7qNv+anUbFuEoP4G |
Date: | Tue, 29 Oct 2013 15:21:54 -0400 |
From: | Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: SIGKILL and TerminateProcess |
Message-ID: | <20131029192154.GB5787@ednor.casa.cgf.cx> |
Reply-To: | cygwin AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
References: | <5F8AAC04F9616747BC4CC0E803D5907D0C40AFEB AT MLBXv04 DOT nih DOT gov> <20131029172205 DOT GA1433 AT ednor DOT casa DOT cgf DOT cx> <5F8AAC04F9616747BC4CC0E803D5907D0C40B0C6 AT MLBXv04 DOT nih DOT gov> |
MIME-Version: | 1.0 |
In-Reply-To: | <5F8AAC04F9616747BC4CC0E803D5907D0C40B0C6@MLBXv04.nih.gov> |
User-Agent: | Mutt/1.5.20 (2009-06-14) |
On Tue, Oct 29, 2013 at 06:37:46PM +0000, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote: >> 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. As the person who wrote the signal handling code, I think I get to specify what I consider to be a redesign. >>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. You may notice that I didn't specify Sleep() in my explanation. >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.. To be a broken record: The whole point of Cygwin is to run UNIX based programs on Windows. Asking for the addition of special-case code so that people can use Windows functions in their programs completely misses the point of this project. That said, however, the Cygwin "kill" command does have a "-f" option which forces the termination of a process if it can't be killed with Cygwin's signal mechanism (I added it so that I could kill processes that were hung while I was working on Cygwin's signal code). If it is essential that you be able to summarily terminate Windows programs then use that. Otherwise, I guarantee that continuing to insist that you need this will avail you naught. Your suggested change is not going to be implemented. cgf -- 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |