From: Dave Mitchell <davem@fdisolutions.com>
Date: Sun, 1 Feb 2004 15:46:24 +0000 (+0000)
Subject: threads documentation: fork on UNIX might not copy all threads.
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=a95a5f75a0e72874474834cd9e274afa0f23b6d8;p=p5sagit%2Fp5-mst-13.2.git

threads documentation: fork on UNIX might not copy all threads.

p4raw-id: //depot/perl@22257
---

diff --git a/pod/perlthrtut.pod b/pod/perlthrtut.pod
index 7cac46f..517fdd1 100644
--- a/pod/perlthrtut.pod
+++ b/pod/perlthrtut.pod
@@ -985,9 +985,10 @@ Further examples of process-scope changes include umask() and
 changing uids/gids.
 
 Thinking of mixing fork() and threads?  Please lie down and wait
-until the feeling passes-- but in case you really want to know,
-the semantics is that fork() duplicates all the threads.
-(In UNIX, at least, other platforms will do something different.)
+until the feeling passes.  Be aware that the semantics of fork() vary
+between platforms.  For example, some UNIX systems copy all the current
+threads into the child process, while others only copy the thread that
+called fork(). You have been warned!
 
 Similarly, mixing signals and threads should not be attempted.
 Implementations are platform-dependent, and even the POSIX