02.07.2013 Views

A/UX® Programmer's Reference Sections

A/UX® Programmer's Reference Sections

A/UX® Programmer's Reference Sections

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

signal(3} signal(3}<br />

SIGCONT 2ge continue after stop (cannot be blocked)<br />

SIGURG 30e urgent condition present on socket<br />

SIGIO 31. I/O is possible on a descriptor (see fcntl(2»<br />

The starred signals in the above list cause a core image if not<br />

caught or ignored (see below).<br />

Signals marked with. are discarded if the action is SIG DFLi<br />

signals marked with t cause the process to stop if the process is<br />

part of 4.2 job control.<br />

Junc is assigned one of three values: SIG DFL, SIG IGN, or a<br />

Junction-address. The actions prescribed by these values are as<br />

follows:<br />

S I G _ D FL - terminate process upon receipt of a signal<br />

Upon receipt of the signal sig, the receiving process is to be<br />

terminated with the following consequences:<br />

February, 1990<br />

RevisionC<br />

All of the receiving process's open file descriptors will<br />

be closed.<br />

If the parent process of the receiving process is executing<br />

a wai t, it will be notified of the termination of the<br />

receiving process and the terminating signal's number<br />

will be made available to the parent process; see<br />

wait(2).<br />

If the parent process of the receiving process is not executing<br />

a w ai t, the receiving process will be<br />

transformed into a zombie process (see exi t(2) for<br />

definition of zombie process).<br />

The parent process ID of each of the receiving<br />

process's existing child processes and zombie processes<br />

will be set to 1. This means the initialization process<br />

(see intro(2» inherits each of these processes.<br />

Each attached shared memory segment is detached and<br />

the value of shIn nattach in the data structure associated<br />

with its shared memory identifier is decremented<br />

by 1.<br />

For each semaphore for which the receiving process<br />

has set a semadj value (see semop(2», that semadj<br />

value is added to the semval of the specified semaphore.<br />

2

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!