From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 37884@debbugs.gnu.org, bernardo.bacic@pobox.com
Subject: bug#37884: 27.0.50; Cannot write to a file in VirtualBox shared directory
Date: Sun, 27 Oct 2019 18:34:06 +0200 [thread overview]
Message-ID: <83k18qrvup.fsf@gnu.org> (raw)
In-Reply-To: <m2r22yp48o.fsf@gmail.com> (message from Robert Pluim on Sun, 27 Oct 2019 17:01:11 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: 37884@debbugs.gnu.org, bernardo.bacic@pobox.com
> Date: Sun, 27 Oct 2019 17:01:11 +0100
>
> >> Eli, if the results come back that using 0664 or similar on lockfiles
> >> resolves this, would you be amenable to such a change?
>
> Eli> I'm not sure I understand the proposal. Is the suggestion to chmod
> Eli> the file to 0644 before calling unlink?
>
> Yes, although of course this is assuming it works, one other option
> could be to just not mess with the file's permissions at all when
> initially creating the lockfile.
AFAIU, the problem is with removing the file? If so, I'd suggest to
do what w32.c does: call unlink as we do now, and if it fails, call
chmod to make it writable and try unlink again. This has an advantage
of not changing anything for filesystems that implement the Posix
semantics.
next prev parent reply other threads:[~2019-10-27 16:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 10:28 bug#37884: 27.0.50; Cannot write to a file in VirtualBox shared directory Bernardo
2019-10-24 16:10 ` Robert Pluim
[not found] ` <87blu2emi3.fsf@pobox.com>
2019-10-27 15:34 ` Robert Pluim
2019-10-27 15:52 ` Eli Zaretskii
2019-10-27 16:01 ` Robert Pluim
2019-10-27 16:34 ` Eli Zaretskii [this message]
2019-10-28 9:23 ` Bernardo
2019-10-28 12:32 ` Robert Pluim
2019-10-29 8:50 ` Bernardo
2019-10-29 9:04 ` Andreas Schwab
2019-10-29 13:41 ` Robert Pluim
2019-10-30 8:44 ` Bernardo
2019-10-30 13:31 ` Robert Pluim
2019-10-30 16:25 ` Eli Zaretskii
2019-10-31 1:41 ` Paul Eggert
2019-10-31 7:38 ` Robert Pluim
2019-10-31 14:37 ` Eli Zaretskii
2019-10-31 21:24 ` Paul Eggert
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=83k18qrvup.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37884@debbugs.gnu.org \
--cc=bernardo.bacic@pobox.com \
--cc=rpluim@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.
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).