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

vfork.2: Explain why the child should not call exit(3) 

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2017-02-06 08:25:36 +01:00
parent f3d0d38ecc
commit 015c503468
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
man2/vfork.2
View File

@ -109,8 +109,11 @@ or it makes a call to
Until that point, the child shares all memory with its parent,
including the stack.
The child must not return from the current function or call
.BR exit (3),
but may call
.BR exit (3)
(which would have the effect of calling exit handlers
established by the parent process and flushing the parent's
.BR stdio (3)
buffers), but may call
.BR _exit (2).
As with