aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2015-03-01 15:57:12 +0100
committerMichael Kerrisk <mtk.manpages@gmail.com>2015-03-02 17:25:57 +0100
commit1533d242958ffb333d9d6d47d9c3f08eeb2cb52b (patch)
tree514732ccd7c8bc0fd7e147e060f8f030c62e4a68
parentbc9e70fad67697ba070de5b54d838197a6e43ba7 (diff)
downloadman-pages-1533d242958ffb333d9d6d47d9c3f08eeb2cb52b.tar.gz
clone.2: Small rewording of explanation of clone() wrt threads
Clone has so many effects that it's an oversimplification to say that the *main* use of clone is to create a thread. (In fact, the use of clone() to create new processes may well be more common, since glibc's fork() is a wrapper that calls clone().) Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
-rw-r--r--man2/clone.22
1 files changed, 1 insertions, 1 deletions
diff --git a/man2/clone.2 b/man2/clone.2
index 4104e443b9..752c01e869 100644
--- a/man2/clone.2
+++ b/man2/clone.2
@@ -104,7 +104,7 @@ But see the description of
.B CLONE_PARENT
below.)
-The main use of
+One use of
.BR clone ()
is to implement threads: multiple threads of control in a program that
run concurrently in a shared memory space.