From: Paul Eggert <eggert@cs.ucla.edu>
To: Daniel Colascione <dancol@dancol.org>
Cc: emacs-devel@gnu.org
Subject: Re: Locking files for CLASH_DETECTION now supported on MS-Windows
Date: Mon, 25 Feb 2013 19:23:07 -0800 [thread overview]
Message-ID: <512C2A9B.10105@cs.ucla.edu> (raw)
In-Reply-To: <512C2144.5080704@dancol.org>
On 02/25/2013 06:43 PM, Daniel Colascione wrote:
> File creation is atomic. File deletion is atomic.
> The lock is signaled by the presence of the file, right?
Not in the recently-added MS-Windows implementation, no.
The lock is signaled by a nonempty file (approximately;
the details are a bit more complicated).
There are races where two Emacs instances can both
grab the lock simultaneously. For example, one Emacs
instance can call create_lock_file with !FORCE and another
with FORCE, and afterwards both Emacs instances
think they own the lock (and the lock file itself
says the !FORCE Emacs owns it).
next prev parent reply other threads:[~2013-02-26 3:23 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 17:43 Locking files for CLASH_DETECTION now supported on MS-Windows Eli Zaretskii
2013-02-25 18:05 ` Paul Eggert
2013-02-25 18:41 ` Eli Zaretskii
2013-02-25 18:56 ` Paul Eggert
2013-02-26 2:03 ` Paul Eggert
2013-02-26 2:43 ` Daniel Colascione
2013-02-26 3:23 ` Paul Eggert [this message]
2013-02-26 4:02 ` Eli Zaretskii
2013-02-26 4:28 ` Daniel Colascione
2013-02-26 17:45 ` Eli Zaretskii
2013-02-26 6:05 ` Paul Eggert
2013-02-26 18:41 ` Eli Zaretskii
2013-02-26 18:51 ` Eli Zaretskii
2013-02-26 4:00 ` Eli Zaretskii
2013-02-26 5:46 ` Paul Eggert
2013-02-26 18:02 ` Eli Zaretskii
2013-02-26 18:17 ` Eli Zaretskii
2013-02-26 22:34 ` Paul Eggert
2013-02-27 4:01 ` Eli Zaretskii
2013-02-27 7:45 ` Paul Eggert
2013-02-27 19:02 ` Eli Zaretskii
2013-02-27 19:01 ` Eli Zaretskii
2013-02-25 19:39 ` Glenn Morris
2013-02-25 19:43 ` Eli Zaretskii
2013-02-25 20:35 ` Stefan Monnier
2013-02-25 22:49 ` Paul Eggert
2013-02-26 3:49 ` Eli Zaretskii
2013-02-26 12:56 ` Richard Stallman
2013-02-26 3:40 ` Eli Zaretskii
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=512C2A9B.10105@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=dancol@dancol.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.