HP-UX Reference (11i v1 05/09) - 5 Miscellaneous Topics (vol 9)

s
signal(5) signal(5)
HP-UX EXTENSIONS
DESCRIPTION
HP-UX supports multiple signal interfaces (see sigaction(2), signal(2), sigvector(2), bsdproc(3C), and
sigset(3C)) that allow a process to specify the action taken upon receipt of a signal. All supported signal
interfaces require specification of a signal, as designated by the Name and Number shown below. Signal
specification can be any of the following except
SIGKILL or SIGSTOP, which cannot be caught or ignored:
Name Number Notes Meaning
SIGILL 04 A,B,C illegal instruction
SIGTRAP 05 A,B,C trace trap
SIGIOT 06 A,B software generated signal
SIGEMT 07 A,B software generated signal
SIGFPE 08 A,B floating point exception
SIGKILL 09 A,D,E,F kill
SIGCLD l8 G death of a child (see
WARNINGS below)
SIGPWR 19
C,G power fail (see WARNINGS below)
SIGIO 22 G asynchronous I/O signal; see select(2)
SIGWINCH 23 G window size change; see termio(7)
SIGURG 29 G urgent data arrived on an I/O channel
SIGLOST 30 A file lock lost (NFS file locking)
The letters in the Notes column in the table above indicate the action taken when the signal is received,
and any special conditions on its use:
A The default action is to terminate the process.
B The default action of terminating the process also generates a core image file if possible.
C The action is not reset to SIG_DFL before calling the signal-catching function.
D The signal cannot be ignored.
E The signal cannot be caught.
F The signal will not be held off from a stopped process.
G The default action is to ignore the signal.
H The default action is to stop the process.
All signal interfaces allow specification of an action that determines what to do upon the receipt of a signal,
and should be one of the following:
SIG_DFL Execute the default action, which varies depending on the signal as described above:
A Terminate the receiving process with all of the consequences outlined in
exit(2).
B If following conditions are met, generate a core image file (see core(4)) in the
current working directory of the receiving process:
• The effective user
ID and the real user ID of the receiving process are
equal.
• The effective group ID and the real group ID of the receiving process
are equal.
• A regular file named core does not exist and can be created, or exists
and is writable.
If the file is created, it has the following properties:
• The file mode is 0666, modified by the file creation mode mask (see
umask(2)).
• The file user ID is equal to the effective user ID of the receiving pro-
cess.
• The file group ID is equal to the effective group ID of the receiving pro-
cess.
Section 5−−350 Hewlett-Packard Company − 1 − HP-UX 11i Version 1: September 2005