From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
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 17:01:11 +0100 [thread overview]
Message-ID: <m2r22yp48o.fsf@gmail.com> (raw)
In-Reply-To: <83lft6rxrs.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 27 Oct 2019 17:52:39 +0200")
>>>>> On Sun, 27 Oct 2019 17:52:39 +0200, Eli Zaretskii <eliz@gnu.org> said:
>> From: Robert Pluim <rpluim@gmail.com>
>> Date: Sun, 27 Oct 2019 16:34:54 +0100
>> Cc: 37884@debbugs.gnu.org
>>
>> 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.
Robert
next prev parent reply other threads:[~2019-10-27 16:01 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 [this message]
2019-10-27 16:34 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2r22yp48o.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=37884@debbugs.gnu.org \
--cc=bernardo.bacic@pobox.com \
--cc=eliz@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.