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

vfork.2: Clarify meaning of "child releases the parent's memory" 

The man page was not explicit about how the memory used by
the child is released back to the parent.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Reported-by: Halesh S <halesh.s@india.com>
This commit is contained in:
Michael Kerrisk 2008-10-29 08:17:14 -05:00
parent a87c4a1da3
commit b4dcb33109
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
man2/vfork.2
View File

@ -23,7 +23,7 @@
.\" 1999-11-10: Merged text taken from the page contributed by
.\" Reed H. Petty (rhp@draper.net)
.\"
.TH VFORK 2 2007-07-26 "Linux" "Linux Programmer's Manual"
.TH VFORK 2 2008-10-29 "Linux" "Linux Programmer's Manual"
.SH NAME
vfork \- create a child process and block parent
.SH SYNOPSIS
@ -94,7 +94,11 @@ but may call
.PP
Signal handlers are inherited, but not shared.
Signals to the parent
arrive after the child releases the parent's memory.
arrive after the child releases the parent's memory
(i.e., after the child calls
.BR _exit (2)
or
.BR execve (2)).
.SS "Historic Description"
Under Linux,
.BR fork (2)