From: Daniel Colascione <dancol@dancol.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>, emacs-devel@gnu.org
Subject: Re: Locking files for CLASH_DETECTION now supported on MS-Windows
Date: Mon, 25 Feb 2013 20:28:35 -0800 [thread overview]
Message-ID: <512C39F3.8050105@dancol.org> (raw)
In-Reply-To: <83d2vniuxv.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]
On 2/25/2013 8:02 PM, Eli Zaretskii wrote:
>> Date: Mon, 25 Feb 2013 18:03:13 -0800
>> From: Paul Eggert <eggert@cs.ucla.edu>
>> CC: emacs-devel@gnu.org
>>
>> One other thought. Part of the reason GNU/POSIXish hosts use
>> symbolic links is that readlink, symlink and unlink
>> are atomic operations. They let Emacs atomically create
>> a lock, test whether a lock exists, and remove a lock. This
>> doesn't seem to be true of the new MS-Windows implementation,
>> which uses open+write+close to create a lock and open+read+close
>> to test whether a lock exists, neither of which is atomic.
>> Is there some way this can be done atomically on MS-Windows?
>
> Why is that important? On Windows, as long as a file is open, no
> other application can write to it or remove the file. Is that the
> "atomic" nature you wanted?
>
>> Are readlink, symlink, and unlink atomic on MS-Windows?
>
> Please define "atomic" for these cases, and I will think about that.
If we really need atomicity under Windows, Transactional NTFS will work for more
users than symbolic links will.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2013-02-26 4:28 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
2013-02-26 4:02 ` Eli Zaretskii
2013-02-26 4:28 ` Daniel Colascione [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=512C39F3.8050105@dancol.org \
--to=dancol@dancol.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).