(split) LDP man-pages の original/ を v3.29 に更新。

[linuxjm/LDP_man-pages.git] / original / man2 / vfork.2

diff --git a/original/man2/vfork.2 b/original/man2/vfork.2
index ef86812..2209cfd 100644 (file)
--- a/original/man2/vfork.2
+++ b/original/man2/vfork.2
@@ -23,7 +23,7 @@
 .\" 1999-11-10: Merged text taken from the page contributed by
 .\" Reed H. Petty (rhp@draper.net)
 .\"
 .\" 1999-11-10: Merged text taken from the page contributed by
 .\" Reed H. Petty (rhp@draper.net)
 .\"

-.TH VFORK 2 2009-06-21 "Linux" "Linux Programmer's Manual"
+.TH VFORK 2 2010-09-20 "Linux" "Linux Programmer's Manual"

 .SH NAME
 vfork \- create a child process and block parent
 .SH SYNOPSIS
 .SH NAME
 vfork \- create a child process and block parent
 .SH SYNOPSIS


@@ -39,7 +39,24 @@ Feature Test Macro Requirements for glibc (see
 .in
 .sp
 .BR vfork ():
 .in
 .sp
 .BR vfork ():

-_BSD_SOURCE || _XOPEN_SOURCE\ >=\ 500
+.ad l
+.RS 4
+.PD 0
+.TP 4
+Since glibc 2.12:
+.nf
+_BSD_SOURCE ||
+    (_XOPEN_SOURCE\ >=\ 500 ||
+        _XOPEN_SOURCE\ &&\ _XOPEN_SOURCE_EXTENDED) &&
+    !(_POSIX_C_SOURCE\ >=\ 200809L || _XOPEN_SOURCE\ >=\ 700)
+.TP 4
+.fi
+Before glibc 2.12:
+_BSD_SOURCE || _XOPEN_SOURCE\ >=\ 500 ||
+_XOPEN_SOURCE\ &&\ _XOPEN_SOURCE_EXTENDED
+.PD
+.RE
+.ad b

 .SH DESCRIPTION
 .SS "Standard Description"
 (From POSIX.1)
 .SH DESCRIPTION
 .SS "Standard Description"
 (From POSIX.1)


@@ -74,7 +91,7 @@ is a special case of
 It is used to create new processes without copying the page tables of
 the parent process.
 It may be useful in performance-sensitive applications
 It is used to create new processes without copying the page tables of
 the parent process.
 It may be useful in performance-sensitive applications

-where a child will be created which then immediately issues an
+where a child is created which then immediately issues an

 .BR execve (2).
 .PP
 .BR vfork ()
 .BR execve (2).
 .PP
 .BR vfork ()


@@ -110,7 +127,7 @@ and to create a unique task structure for the child.
 However, in the bad old days a
 .BR fork (2)
 would require making a complete copy of the caller's data space,
 However, in the bad old days a
 .BR fork (2)
 would require making a complete copy of the caller's data space,

-often needlessly, since usually immediately afterwards an
+often needlessly, since usually immediately afterward an

 .BR exec (3)
 is done.
 Thus, for greater efficiency, BSD introduced the
 .BR exec (3)
 is done.
 Thus, for greater efficiency, BSD introduced the


@@ -125,7 +142,7 @@ child was using its resources.
 The use of
 .BR vfork ()
 was tricky: for example, not modifying data
 The use of
 .BR vfork ()
 was tricky: for example, not modifying data

-in the parent process depended on knowing which variables are
+in the parent process depended on knowing which variables were

 held in a register.
 .SH "CONFORMING TO"
 4.3BSD, POSIX.1-2001.
 held in a register.
 .SH "CONFORMING TO"
 4.3BSD, POSIX.1-2001.