This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Avoid sending SIGINT to native child process?
- From: Thomas Wolff <towo at towo dot net>
- To: cygwin at cygwin dot com
- Date: Sat, 29 Apr 2017 08:18:59 +0200
- Subject: Re: Avoid sending SIGINT to native child process?
- Authentication-results: sourceware.org; auth=none
- References: <c9aab181-aa6d-f724-9f1e-2497b16609f6@acm.org>
Am 29.04.2017 um 04:33 schrieb David Rothenberger:
Is there any way to prevent a SIGINT signal from propagating to a
background child Windows process?
I'm trying to write a script to start a Java application server. I
want the script to trap Ctrl-C and send the app server a command to
shutdown cleanly, but it appears the Ctrl-C is immediately propagated
to the Java process, even though the script traps it.
Signal handling interoperability is lacking more generally.
Even SIGTSTP is propagated in such a way that the Windows application is
terminated.
(Try running notepad from bash, then type Ctrl-Z.)
Thomas
--
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