Open System Services System Calls Reference Manual (G06.29+, H06.08+, J06.03+)

Files signal(4)
Note: The process terminates and, where possible, a saveabend (core) file is created on genera-
tion of any signal if both of the following conditions are true:
• The signal was generated as a result of something other than the kill() or raise()
function.
• Either the signal is blocked or ignored, or the process is in operating system code
when the signal is generated.
The _POSIX_JOB_CONTROL symbolic constant is always defined. Hence, the job control sig-
nals are all supported: SIGCHLD, SIGCONT, SIGSTOP, SIGTSTP, SIGTTIN, and
SIGTTOU.
Default Action
The default action for a signal occurs when the signal is not blocked and one of the following is
true:
• No signal-catching function is installed for that signal.
• A signal-catching function is installed for the signal, but the SIG_DFL action is
specified.
The table under The Signals, earlier, indicates a default action for each signal. The default
actions have the following meanings:
Terminate process
Terminate the receiving process with all the consequences described for the
_exit() function.
Terminate with saveabend
Terminate the receiving process with all the consequences described for the
_exit() function. Create a memory image file (saveabend file) in the current
directory of the receiving process if the following conditions are met:
• The effective user ID and the real user ID of the receiving process are
equal.
• A regular file named ZZSAnnnn (the saveabend file) can be created in
the current directory. The file will have the following properties:
— The access permission code 0666 (0x1B6), modified by the
filemode creation mask (see the umask(2) reference page)
— A file owner ID that is the same as the effective user ID of the
receiving process
— A file group ID that is the same as the effective group ID of the
receiving process
Note that the location of the saveabend file is different in the OSS
environment than in the Guardian environment. In the Guardian
environment, the file is created on the same subvolume as the program
file. In the OSS environment, the file is created in the current working
directory.
Saveabend files are known on most UNIX systems as core files.
527186-023 Hewlett-Packard Company 11−35