From: Ranjan Bagchi <ranjan.bagchi@frotz.com>
To: caml-list@inria.fr
Subject: [Caml-list] Best way to synchronize OS processes?
Date: Tue, 11 May 2004 11:05:23 -0700 [thread overview]
Message-ID: <40A115E3.1060400@frotz.com> (raw)
Hi --
I'm writing some code which will end up executing concurrently on
several OS processes. I'd like to serialize access to some specific OS
resources (for instance, writing to a single file). The Unix module
doesn't appear to offer anything like a critical section or an OS
mutex. Is there a preferred way to do this?
Thanks,
Ranjan
-------------------
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
next reply other threads:[~2004-05-11 18:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 18:05 Ranjan Bagchi [this message]
2004-05-11 18:09 ` Shawn Wagner
2004-05-11 18:24 ` Ranjan Bagchi
2004-05-12 7:01 ` Jean-Christophe Filliatre
2004-05-12 16:35 ` Ranjan Bagchi
2004-05-12 11:27 ` Alex Baretta
2004-05-12 11:46 ` Ville-Pertti Keinonen
2004-05-12 13:16 ` Olivier Andrieu
2004-05-12 12:53 ` Gerd Stolpmann
2004-05-11 18:10 ` Richard Jones
2004-05-12 16:52 ` Shawn Wagner
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=40A115E3.1060400@frotz.com \
--to=ranjan.bagchi@frotz.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