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>

diff --git a/man2/vfork.2 b/man2/vfork.2
index 55044ad5f000ffde516e122101357b25e4c84472..6cd838fc517325b0faae0debce5f7b645fcc8cae 100644 (file)
--- a/man2/vfork.2
+++ b/man2/vfork.2
@@ -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)