summaryrefslogtreecommitdiffstats
path: root/man2/vfork.2
diff options
context:
space:
mode:
Diffstat (limited to 'man2/vfork.2')
-rw-r--r--man2/vfork.29
1 files changed, 4 insertions, 5 deletions
diff --git a/man2/vfork.2 b/man2/vfork.2
index 3a65010ca..c2b18fcf2 100644
--- a/man2/vfork.2
+++ b/man2/vfork.2
@@ -149,13 +149,12 @@ and cannot rely on any specific behavior with respect to shared memory.
Some consider the semantics of
.BR vfork ()
to be an architectural blemish, and the 4.2BSD man page stated:
-"This system call will be eliminated when proper system sharing mechanisms
-are implemented.
+\[lq]This system call will be eliminated
+when proper system sharing mechanisms are implemented.
Users should not depend on the memory sharing semantics of
-.BR vfork ()
+.I vfork
as it will, in that case, be made synonymous to
-.BR fork (2).\c
-"
+.IR fork .\[rq]
However, even though modern memory management hardware
has decreased the performance difference between
.BR fork (2)