From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id NAA03924; Mon, 19 May 2003 13:37:56 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id NAA02230 for ; Mon, 19 May 2003 13:37:55 +0200 (MET DST) Received: from mail2.telekom.de (mail2.telekom.de [195.243.210.210]) by nez-perce.inria.fr (8.11.1/8.11.1) with ESMTP id h4JBbsT28460 for ; Mon, 19 May 2003 13:37:54 +0200 (MET DST) Received: from g8pxb.blf01.telekom.de by mail2.dmz.telekom.de with ESMTP for caml-list@inria.fr; Mon, 19 May 2003 13:20:50 +0200 Received: from mail2.dmz.telekom.de (mail2.dmz.telekom.de [192.168.89.11]) by g8pxb.blf01.telekom.de with ESMTP for caml-list@inria.fr; Mon, 19 May 2003 13:21:18 +0200 Received: from g9jbr.mgb01.telekom.de by mail2.dmz.telekom.de with ESMTP for caml-list@inria.fr; Mon, 19 May 2003 13:07:47 +0200 Received: by G9JBR.mgb01.telekom.de with Internet Mail Service (5.5.2653.19) id ; Mon, 19 May 2003 13:07:50 +0200 Message-Id: From: "Beck01, Wolfgang" To: caml-list@inria.fr Subject: RE: [Caml-list] different behaviour of Unix.fork on FreeBSD and L inux Date: Mon, 19 May 2003 13:07:49 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam: no; 0.00; t-systems:01 caml-list:01 fork:01 printf:01 stdout:01 forking:01 buffering:01 flush:01 behaviour:01 remi:01 unix:02 wolfgang:02 beck:04 explained:05 output:05 Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk > > it is a problem of bufferisation of the output made by printf. If you > flush stdout before forking, there will be no problem. > Thank you Remi and John. This makes sense. However, I've inserted the printf's to trace down an error that occurs under Linux but not under FreeBSD and that can't be explained with stdout buffering effects. I was hoping the reasons of the strange printf behaviour would also explain the other error I get. -- Wolfgang Beck T-Systems Nova GmbH ------------------- To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/ Beginner's list: http://groups.yahoo.com/group/ocaml_beginners