From: John Carr <jfc@MIT.EDU>
To: "Beck01, Wolfgang" <BeckW@t-systems.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] different behaviour of Unix.fork on FreeBSD and Linux
Date: Mon, 19 May 2003 06:03:58 -0400 [thread overview]
Message-ID: <200305191003.GAA17246@nerd-xing.mit.edu> (raw)
In-Reply-To: Your message of "Mon, 19 May 2003 11:35:59 +0200." <D971A27FCD3DE04689089E8A98D8AF7107C308@G9JJ1.mgb01.telekom.de>
fork duplicates the buffers holding output that has not yet been
written to a file descriptor. If the output buffer is not empty
at the time of fork, output may be duplicated.
If output is unbuffered or line buffered the program will work
as in the BSD case. Otherwise you need to arrange for buffered
output to be written before fork().
In C one is advised to call fflush(NULL) before fork if the child does
I/O. If the child calls exec() immediately _exit() should be used
instead of exit() if the exec() fails. (_exit() terminates the
process without flushing I/O buffers.)
-------------------
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
prev parent reply other threads:[~2003-05-19 10:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 9:35 Beck01, Wolfgang
2003-05-19 10:03 ` Remi Vanicat
2003-05-19 10:03 ` John Carr [this message]
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=200305191003.GAA17246@nerd-xing.mit.edu \
--to=jfc@mit.edu \
--cc=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).