- do not call pthread_atfork(3) handlers when a multithreaded program

calls vfork(2). "untested, but looks OK" marc@
- document vfork(2), popen(3) and system(3) don't call atfork handlers
in multithreaded programs. okay jmc@

1 files changed, 6 insertions, 2 deletions

diff --git a/lib/libc/sys/vfork.2 b/lib/libc/sys/vfork.2
index c1b4b6ec798..ec0e5a75639 100644
--- a/lib/libc/sys/vfork.2
+++ b/lib/libc/sys/vfork.2
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: vfork.2,v 1.15 2007/05/31 19:19:34 jmc Exp $
+.\"	$OpenBSD: vfork.2,v 1.16 2008/04/04 19:30:41 kurt Exp $
 .\"	$NetBSD: vfork.2,v 1.8 1997/07/10 07:54:13 mikel Exp $
 .\"
 .\" Copyright (c) 1980, 1991, 1993
@@ -30,7 +30,7 @@
 .\"
 .\"     @(#)vfork.2	8.1 (Berkeley) 6/4/93
 .\"
-.Dd $Mdocdate: May 31 2007 $
+.Dd $Mdocdate: April 4 2008 $
 .Dt VFORK 2
 .Os
 .Sh NAME
@@ -62,6 +62,10 @@ in that the parent is suspended until the child makes a call to
 or an exit (either by a call to
 .Xr _exit 2
 or abnormally).
+In addition, fork handlers established using
+.Xr pthread_atfork 3
+are not called when a multithreaded program calls
+.Fn vfork .
 .Pp
 .Fn vfork
 returns 0 in the child's context and (later) the PID of the child in