<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Mar 31, 2016 at 11:56 AM, Rainer Müller <span dir="ltr"><<a href="mailto:raimue@macports.org" target="_blank">raimue@macports.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":1fa" class="a3s" style="overflow:hidden">A better way could be to handle SIGINT/SIGQUIT in a custom handler and<br>
on reception of a signal, we would kill the child process and return the<br>
error {POSIX SIG SIGINT} as result of SystemCmd. However, I am unsure<br>
how we would force the child to terminate and if this can be done reliably.<br></div></blockquote></div><br>Seems to me you want an altered version of the old way: instead of printing a message, set an "interrupted by user" flag and resume waiting for the child, then ignore the child exit and return your "interrupted by user" status.<br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div><div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div></div>
</div></div>