[PATCH] vfork.2: Add sentence explaining what is done to data space copy after exec(3)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>From d12bf2ad1cbf72c4b4bc6913e1ce8077333bade0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20Goddard=20Rosa?= <andre.goddard@xxxxxxxxx>
Date: Mon, 7 Sep 2009 11:19:36 -0300
Subject: [PATCH] vfork.2: Add sentence explaining what is done to data
space copy after exec(3)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Explain that in case exec() is done immediately after vfork(), the data
space copy has a very limited lifespan, being discarded afterwards.

Signed-off-by: André Goddard Rosa <andre.goddard@xxxxxxxxx>

diff --git a/man2/vfork.2 b/man2/vfork.2
index ef86812..6dc1c28 100644
--- a/man2/vfork.2
+++ b/man2/vfork.2
@@ -110,7 +110,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,
-often needlessly, since usually immediately afterwards an
+often needlessly, since usually it's discarded immediately afterwards an
 .BR exec (3)
 is done.
 Thus, for greater efficiency, BSD introduced the
-- 
1.6.4.2.268.g6ea71
From d12bf2ad1cbf72c4b4bc6913e1ce8077333bade0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20Goddard=20Rosa?= <andre.goddard@xxxxxxxxx>
Date: Mon, 7 Sep 2009 11:19:36 -0300
Subject: [PATCH] vfork.2: Add sentence explaining what is done to data space copy after exec(3)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Explain that in case exec() is done immediately after vfork(), the data
space copy has a very limited lifespan, being discarded afterwards.

Signed-off-by: André Goddard Rosa <andre.goddard@xxxxxxxxx>

diff --git a/man2/vfork.2 b/man2/vfork.2
index ef86812..6dc1c28 100644
--- a/man2/vfork.2
+++ b/man2/vfork.2
@@ -110,7 +110,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,
-often needlessly, since usually immediately afterwards an
+often needlessly, since usually it's discarded immediately afterwards an
 .BR exec (3)
 is done.
 Thus, for greater efficiency, BSD introduced the
-- 
1.6.4.2.268.g6ea71


[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux