LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

tripped some excess/outdated text from the BUGS section.

This commit is contained in:
Michael Kerrisk 2007-03-06 06:37:48 +00:00
parent 87f434dfce
commit 0579929938
1 changed files with 9 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
man2/vfork.2
View File

@ -119,13 +119,6 @@ as it will, in that case, be made synonymous to
.BR fork ().\c
"
Formally speaking, the standard description given above does not allow
one to use
.BR vfork ()
since a following
.BR exec ()
might fail, and then what happens is undefined.
Details of the signal handling are obscure and differ between systems.
The BSD manpage states:
"To avoid a possible deadlock situation, processes that are children
@ -134,12 +127,13 @@ in the middle of a
are never sent SIGTTOU or SIGTTIN signals; rather, output or
.IR ioctl s
are allowed and input attempts result in an end-of-file indication."
Currently (Linux 2.3.25),
.BR strace (1)
cannot follow
.BR vfork ()
and requires a kernel patch.
.\"
.\" As far as I can tell, the following is not true in 2.6.19:
.\" Currently (Linux 2.3.25),
.\" .BR strace (1)
.\" cannot follow
.\" .BR vfork ()
.\" and requires a kernel patch.
.SH HISTORY
The
.BR vfork ()
@ -157,7 +151,8 @@ other architectures) it is an independent system call. Support was
added in glibc 2.0.112.
.SH "CONFORMING TO"
4.3BSD, POSIX.1-2001.
.\" FIXME Mar 07: in the draft of the next POSIX revision, the spec for
.\" vfork() has been removed.
The requirements put on
.BR vfork ()
by the standards are weaker than those put on