diff options
| author | Dave Mitchell <davem@fdisolutions.com> | 2004-02-01 15:46:24 +0000 |
|---|---|---|
| committer | Dave Mitchell <davem@fdisolutions.com> | 2004-02-01 15:46:24 +0000 |
| commit | a95a5f75a0e72874474834cd9e274afa0f23b6d8 (patch) | |
| tree | bc15d93e3012687ccc5e5ad77f662f8cb8edfecb /pod/perlthrtut.pod | |
| parent | 687305a06dbeb1a5ae2ba1c76df272db4e96667a (diff) | |
| download | perl-a95a5f75a0e72874474834cd9e274afa0f23b6d8.tar.gz | |
threads documentation: fork on UNIX might not copy all threads.
p4raw-id: //depot/perl@22257
Diffstat (limited to 'pod/perlthrtut.pod')
| -rw-r--r-- | pod/perlthrtut.pod | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/pod/perlthrtut.pod b/pod/perlthrtut.pod index 7cac46fc55..517fdd1b86 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 |