caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: David MENTRE <dmentre@linux-france.org>
To: matthieu.dubuget@gmail.com
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] file mapped bigarray and Unix.unlink
Date: Thu, 2 Jul 2009 11:49:33 +0200	[thread overview]
Message-ID: <3d13dcfc0907020249w355b8bf1o1f53b7c324fd0423@mail.gmail.com> (raw)
In-Reply-To: <4A4C75D2.9060503@gmail.com>

Hello Mathieu,

2009/7/2 Matthieu Dubuget <matthieu.dubuget@gmail.com>:
> The strategy I adopted is to spawn a recursive thread that
> periodically try to erase the file until success.

That seems the wrong solution to me. The unlink syscall should work
immediately or you have another reason why it only works after a
certain time.

Yours,
david


  reply	other threads:[~2009-07-02  9:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02  8:10 Matthieu Dubuget
2009-07-02  8:54 ` [Caml-list] " Matthieu Dubuget
2009-07-02  9:49   ` David MENTRE [this message]
2009-07-02 10:15     ` Matthieu Dubuget
2009-07-02 12:48 ` Florian Hars
2009-07-02 12:43 Dario Teixeira

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=3d13dcfc0907020249w355b8bf1o1f53b7c324fd0423@mail.gmail.com \
    --to=dmentre@linux-france.org \
    --cc=caml-list@inria.fr \
    --cc=matthieu.dubuget@gmail.com \
    /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).