This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: kill -2 is too powerful
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 13 Jul 2007 10:29:24 -0400
- Subject: Re: kill -2 is too powerful
- References: <11574352.post@talk.nabble.com>
- Reply-to: cygwin at cygwin dot com
On Thu, Jul 12, 2007 at 11:58:15PM -0700, patrickinminneapolis wrote:
>I have a VB.net Console App which catches "Ctrl-C" and then gives the
>user an option "e(x)it \ (r)un". I learned that I needed to set CYGWIN
>= "notty" and so now the console app catches Ctrl-C properly within a
>Cygwin console. I need to run the program as a service however, net
>start IB, and then I use pslist to view its process number and do a
>kill -2 PID I was hoping for my exit/run prompt, but it terminated
>instead. Does anyone know what's going on or a better way to do this
>without reprogramming the VB.NET code?
Cygwin kills non-cygwin processes when it is processing an unhandled
CTRL-C. It's worked that way for years and I, for one, rely on that
behavior.
This is one case where we can't accommodate native windows programs
perfectly.
--
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/