caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Alex Baretta <alex@baretta.com>
To: Shawn Wagner <shawnw@speakeasy.org>
Cc: caml-list@inria.fr, ranjan.bagchi@frotz.com
Subject: Re: [Caml-list] Best way to synchronize OS processes?
Date: Wed, 12 May 2004 13:27:11 +0200	[thread overview]
Message-ID: <40A20A0F.2070809@baretta.com> (raw)
In-Reply-To: <20040511180933.GB595@speakeasy.org>

Shawn Wagner wrote:
> On Tue, May 11, 2004 at 11:05:23AM -0700, Ranjan Bagchi wrote:
> 
>>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?
> 
> 
> File locking with Unix.lockf?

I disagree. I faced the same problem and found that it cannot be easily 
solved with lockf. Unix.lockf locks specific regions in a file, whereas 
Ranjan seems to need the equivalent of a mutex, which should be 
implemented as a lock over the entire file. This is done by the flock 
primitive in Posix systems. Unluckily, flock has not been included in 
the Unix module.

I have written my own Flock module, which might be useful to Rajan. It 
supports locking Pervasive channels as well as locking the underlying 
file descriptors. I have sent it to Caml team as a contribution to the 
Unix module, but apparently it was not accepted.

I'm willing to send it to anyone requesting it. Note that it is released 
under the GPL--not the LGPL--so licensing issues might arise.

Alex

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


  parent reply	other threads:[~2004-05-12 11:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-11 18:05 Ranjan Bagchi
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 [this message]
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=40A20A0F.2070809@baretta.com \
    --to=alex@baretta.com \
    --cc=caml-list@inria.fr \
    --cc=ranjan.bagchi@frotz.com \
    --cc=shawnw@speakeasy.org \
    /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).