From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Locking files for CLASH_DETECTION now supported on MS-Windows
Date: Tue, 26 Feb 2013 23:45:38 -0800 [thread overview]
Message-ID: <512DB9A2.7020409@cs.ucla.edu> (raw)
In-Reply-To: <83zjyqwgk7.fsf@gnu.org>
>>> We could avoid this by teaching Emacs on Posix systems to
>>> read lock files created by Emacs running on Windows.
>>
>> I don't see how to do this without introducing race
>> conditions that are not present in the current GNU/Linux
>> implementation.
>
> Can you describe those race conditions? I'm talking only about
> _reading_ those files, not about creating them.
Sorry, I must have misunderstood you.
There are no races if access is read-only. We need at least one
writer (i.e., one process that's either creating or removing a
lock file) in order to have a race. I thought the original
scenario involved an MS-Windows Emacs locking a file at about
the same time that a GNU/Linux Emacs locks the same file.
> The changes you are promoting cause Emacs to take control of any
> file whose name matches the pattern .#FILE, where FILE is the file we edit.
No, under that proposal, if there's an existing non-symlink
.#FILE then Emacs doesn't lock FILE; it simply bypasses
locking for FILE for entirely and it doesn't modify .#FILE
at all. This should be relatively rare.
It is true that if there's an existing symlink .#FILE then Emacs
will take control of it when it edits FILE, but that should be OK.
>>> Another possibility would be to make Emacs running on Windows avoid
>>> locking files on remote filesystems.
>>
>> Won't there still be a problem if the local file system is
>> exported?
>
> No, because such exported systems will not support symlinks from Posix
> hosts.
I thought that such symlinks were supported: the lock would appear to be a regular file
on the MS-Windows server side, but as exported over the network it would
appear to be a symbolic link on the GNU/Linux client side, as that's
how the Microsoft server software works. If the MS-Windows
and GNU/Linux locks have the same name, they'd collide
I presume.
>> To move things forward, I propose that the MS-Windows
>> implementation use a different lock file name .#-FOO.
>
> I don't mind, but I thought we could do better.
It's possible that we can do better, but I'm afraid that'll
take some work. In the meantime I plan to go ahead with that
proposal as it's better than what we have now.
next prev parent reply other threads:[~2013-02-27 7:45 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
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 [this message]
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=512DB9A2.7020409@cs.ucla.edu \
--to=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 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.