From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by yquem.inria.fr (Postfix) with ESMTP id 5BCA0BB9C for ; Tue, 22 Nov 2005 17:01:57 +0100 (CET) Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35]) by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id jAMG1u4S017221 for ; Tue, 22 Nov 2005 17:01:57 +0100 Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id RAA15170 for ; Tue, 22 Nov 2005 17:01:56 +0100 (MET) Received: from lynndie.uscs.susx.ac.uk (lynndie.uscs.susx.ac.uk [139.184.14.87]) by concorde.inria.fr (8.13.0/8.13.0) with ESMTP id jAMG1uA2008704 for ; Tue, 22 Nov 2005 17:01:56 +0100 Received: from calaf.rn.informatics.scitech.susx.ac.uk ([139.184.48.199]:53099) by lynndie.uscs.susx.ac.uk with esmtp (Exim 4.43) id IQD5V7-00014C-I5 for caml-list@inria.fr; Tue, 22 Nov 2005 16:01:55 +0000 Subject: Re: [Caml-list] Threads & Fork From: David Teller To: caml-list@inria.fr In-Reply-To: <20051122155002.GB16451@first.in-berlin.de> References: <1132673981.13170.17.camel@starlight> <87wtj07kv8.fsf@mid.deneb.enyo.de> <20051122155002.GB16451@first.in-berlin.de> Content-Type: text/plain Date: Tue, 22 Nov 2005 16:01:48 +0000 Message-Id: <1132675308.26632.17.camel@calaf.rn.informatics.scitech.susx.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-22) Content-Transfer-Encoding: 7bit X-Sussex: true X-Miltered: at nez-perce with ID 438340F5.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Miltered: at concorde with ID 438340F4.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Spam: no; 0.00; caml-list:01 threads:01 oliver:01 bandel:01 threads:01 posix:01 api:01 threadunix:01 non-blocking:01 cheers:01 unix:01 wrote:01 thread:02 external:02 handles:03 X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.0.3 On Tue, 2005-11-22 at 16:50 +0100, Oliver Bandel wrote: > I doubt that this is true. > Unix-fork() copies a complete process. > If the original has threads, the copy also have. > I don't think that POSIX handles this different to old Unix API. Er... that would depend on the implementation of threads. Some thread libraries rely on external processes and shared memory. I don't know how ThreadUnix works to provide non-blocking system calls, but that might be one source of the problem. Cheers, David