Mike Hall wrote
>>Nope. Whether an application responds (or not) to a signal is entirely up
>>to the application.
>
>... But again I don't see how this is up to the application.
On Unix-alikes, applications can catch, ignore, or default any signal
except SIGKILL. If a signal is ignored or defaulted, child processes
inherit that. Signals that are caught by a process are defaulted in a
child of that process.
On Windows, I think it's pretty much the same, though the signals
themselves are somewhat different.
Java programs on Mac OS X can access signal-disposition (catch, ignore,
default) and signal-sending (process, process-group, user) using either my
Suite/P Toolkit or Easy Posix Toolkit:
<http://www.amug.org/~glguerin/sw/#suitep>
<http://www.amug.org/~glguerin/sw/#easyposix>
FWIW, one can also ignore signals in a shell-script (Bourne-lineage, not
csh-lineage), which would then be inherited by a child process, such as the
'java' command.
There's also the -Xrs option to 'java' which omits the SIGQUIT handler, and
also omits the setting of SIGPIPE to be ignored.
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
