caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Beck01, Wolfgang" <BeckW@t-systems.com>
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	[thread overview]
Message-ID: <D971A27FCD3DE04689089E8A98D8AF7107C309@G9JJ1.mgb01.telekom.de> (raw)



> 
> 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


                 reply	other threads:[~2003-05-19 11:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D971A27FCD3DE04689089E8A98D8AF7107C309@G9JJ1.mgb01.telekom.de \
    --to=beckw@t-systems.com \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).