Contents Previous Next
Signals Used in Oracle Solaris and Linux
Table 7-2 Signals Used on Oracle Solaris and Linux
| Signal | Description |
|---|---|
|
|
These signals are used in the implementation for implicit null check, and so forth. |
|
|
This signal is used to dump Java stack traces to the standard error stream. (Optional) |
|
|
These signals are used to support the shutdown hook mechanism ( |
|
|
This signal is used in the implementation of the |
|
|
This signal is used internally. Not used starting with Oracle Solaris 10 operating system. (Configurable) |
|
|
The HotSpot VM does not handle this signal. Instead it calls the |
Signals tagged as "optional" are not used when the -Xrs option is specified to reduce signal usage. With this option fewer signals are used, although the VM installs its own signal handler for essential signals such as SIGSEGV. Specifying this option means that the shutdown hook mechanism will not execute if the process receives a SIGQUIT, SIGTERM, SIGINT, or SIGHUP. Shutdown hooks will execute, as expected, if the VM terminates normally (that is, when the last non-daemon thread completes or the System.exit method is invoked).
On Oracle Solaris 8 and 9 operating system, signals tagged as "configurable" are substituted when the -XX:+UseAltSigs option is specified to use alternative signals. Starting with Oracle Solaris 10 operating system, this option is ignored, as the operating system reserves two additional signals (called SIGJVM1 and SIGJVM2).
On Linux, the handler for SIGUSR1 cannot be overridden. SIGUSR2 is used to implement suspend and resume. However it is possible to specify an alternative signal to be used instead of SIGUSR2. This is done by specifying the _JAVA_SR_SIGNUM environment variable. If this environment variable is set, it must be set to a value larger than the maximum of SIGSEGV and SIGBUS.