Date: Fri, 13 Jul 2007 10:29:24 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: kill -2 is too powerful
Message-ID: <20070713142924.GD13962@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <11574352 DOT post AT talk DOT nabble DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <11574352.post@talk.nabble.com>
User-Agent: Mutt/1.5.15 (2007-04-06)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-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/