Added waitid(); added SA_NOCLDSTOP; updated SA_NOCLDWAIT; much other text rewritten

This commit is contained in:
Michael Kerrisk 2004-11-11 14:40:35 +00:00
parent fe4992a761
commit d3b2ef5de2
1 changed files with 12 additions and 12 deletions

View File

@ -79,7 +79,7 @@ flag of
.BR sigaction (2)).
In the remainder of this page, a child whose state has changed
and which has not yet been waited upon by one of these system
calls is said termed
calls is termed
.IR waitable .
.SS "wait() and waitpid()"
The
@ -132,18 +132,18 @@ is an OR of zero or more of the following constants:
return immediately if no child has exited.
.TP
.B WUNTRACED
also return for children which are stopped
also return if a child has stopped
(but not traced via
.BR ptrace (2)),
and whose status has not been reported.
Status for traced children which are stopped is provided
also without this option.
.BR ptrace (2)).
Status for
.I traced
children which have stopped is provided
even if this option is not specified.
.TP
.B WCONTINUED
(Since Linux 2.6.10)
.\" FIXME WCONTINUED *should* be in 2.6.10 -- MTK, Nov 04
also return for stopped children that have been resumed
by delivery of
also return if a stopped child has been resumed by delivery of
.BR SIGCONT .
.PP
(For Linux-only options, see below.)
@ -337,11 +337,11 @@ field before the call and check for a non-zero value in this field
after the call returns.
.SH "RETURN VALUE"
.BR wait ():
on successs, returns the PID of the terminated child;
on success, returns the process ID of the terminated child;
on error, \-1 is returned.
.BR waitpid():
on success, returns the PID of the child whose state has changed;
on success, returns the process ID of the child whose state has changed;
on error, \-1 is returned;
if
.B WNOHANG
@ -434,8 +434,8 @@ call is made while
.B SIGCHLD
is being ignored, the call behaves just as though
.B SIGCHLD
were not being igored, that is, the call blocks until the next
child terminates and then returns the PID and status of that child.
were not being ingored, that is, the call blocks until the next child
terminates and then returns the process ID and status of that child.
.SH "LINUX NOTES"
In the Linux kernel, a kernel-scheduled thread is not a distinct
construct from a process. Instead, a thread is simply a process