From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: Avoid sending SIGINT to native child process?
Date: Sun, 30 Apr 2017 17:30:00 -0000 [thread overview]
Message-ID: <e28e883a-fd20-e761-0a4e-cc58ae6bd784@towo.net> (raw)
In-Reply-To: <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
prev parent reply other threads:[~2017-04-29 6:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 13:12 David Rothenberger
2017-04-30 17:30 ` Thomas Wolff [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e28e883a-fd20-e761-0a4e-cc58ae6bd784@towo.net \
--to=towo@towo.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).