aboutsummaryrefslogtreecommitdiff
path: root/manual/process.texi
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>1999-01-24 10:17:23 +0000
committerUlrich Drepper <drepper@redhat.com>1999-01-24 10:17:23 +0000
commit440d13e289b6716dd5105d7209107da6821ce1b4 (patch)
tree43cd287039bc51e7ad1cf3150724a46090d2e6f4 /manual/process.texi
parentd74e76f9f6b05428358a6248ac506dc38c323c7e (diff)
downloadglibc-440d13e289b6716dd5105d7209107da6821ce1b4.tar
glibc-440d13e289b6716dd5105d7209107da6821ce1b4.tar.gz
glibc-440d13e289b6716dd5105d7209107da6821ce1b4.tar.bz2
glibc-440d13e289b6716dd5105d7209107da6821ce1b4.zip
Update.
1999-01-24 Ulrich Drepper <drepper@cygnus.com> * ctype/ctype.c (toupper): Correct variable names from lat change. (tolower): Likewise.
Diffstat (limited to 'manual/process.texi')
-rw-r--r--manual/process.texi14
1 files changed, 7 insertions, 7 deletions
diff --git a/manual/process.texi b/manual/process.texi
index 46aeff6009..14421b592f 100644
--- a/manual/process.texi
+++ b/manual/process.texi
@@ -243,15 +243,15 @@ signals and signal actions from the parent process.)
@comment unistd.h
@comment BSD
@deftypefun pid_t vfork (void)
-The @code{vfork} function is similar to @code{fork} but on systems it
-is more efficient; however, there are restrictions you must follow to
+The @code{vfork} function is similar to @code{fork} but on some systems
+it is more efficient; however, there are restrictions you must follow to
use it safely.
-While @code{fork} makes a complete copy of the calling process's
-address space and allows both the parent and child to execute
-independently, @code{vfork} does not make this copy. Instead, the
-child process created with @code{vfork} shares its parent's address
-space until it calls exits or one of the @code{exec} functions. In the
+While @code{fork} makes a complete copy of the calling process's address
+space and allows both the parent and child to execute independently,
+@code{vfork} does not make this copy. Instead, the child process
+created with @code{vfork} shares its parent's address space until it
+calls @code{_exit} or one of the @code{exec} functions. In the
meantime, the parent process suspends execution.
You must be very careful not to allow the child process created with