HP-UX Reference (11i v3 07/02) - 2 System Calls (vol 5)

w
wait(2) wait(2)
WARNINGS
HP-UX EXTENSION: The operation of wait(), waitpid()
is affected if the SIGCLD signal is set to
SIG_IGN (see the WARNINGS section of signal(5)). Signal handlers that cause system calls to be res-
tarted can affect the [EINTR] condition (see bsdproc(3C) and sigaction(2)).
APPLICATION USAGE
Threads Considerations
In a multithreaded application, only the calling thread is suspended by
wait(),
waitpid() call.
wait() and waitpid() will not return until all threads in the process have reached the desired state.
For example, the wait(),
waitpid() calls will not return until all threads have terminated. If the
WUNTRACED or WCONTINUED options are specified for the
waitpid() call, it will not return until all
threads have stopped or continued, respectively.
SEE ALSO
Exit conditions (
$?)insh(1), exec(2), exit(2), fork(2), pause(2), ttrace (2), wait3(2), waitid(2), signal(5),
<sys/types.h>
, <sys/wait.h> .
AUTHOR
wait(), waitpid(), and wait3() were developed by HP, AT&T and the University of California,
Berkeley.
STANDARDS CONFORMANCE
wait(): AES, SVID2, SVID3, XPG2, XPG3, XPG4, FIPS 151-2, POSIX.1
waitpid(): AES, SVID3, XPG3, XPG4, FIPS 151-2, POSIX.1
HP-UX 11i Version 3: February 2007 − 4 − Hewlett-Packard Company 545