From b4dcb33109f49969d559c7f901d979f46bf270b9 Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Wed, 29 Oct 2008 08:17:14 -0500 Subject: [PATCH] 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 Reported-by: Halesh S --- man2/vfork.2 | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/man2/vfork.2 b/man2/vfork.2 index 55044ad5f..6cd838fc5 100644 --- 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)