From: Robert Pluim <rpluim@gmail.com>
To: Bernardo <bernardo.bacic@pobox.com>
Cc: 37884@debbugs.gnu.org
Subject: bug#37884: 27.0.50; Cannot write to a file in VirtualBox shared directory
Date: Sun, 27 Oct 2019 16:34:54 +0100 [thread overview]
Message-ID: <m2y2x6p5gh.fsf@gmail.com> (raw)
In-Reply-To: <87blu2emi3.fsf@pobox.com> (Bernardo's message of "Sun, 27 Oct 2019 17:22:12 +1100")
Please keep 37884@debbugs.gnu.org in the CC
>>>>> On Sun, 27 Oct 2019 17:22:12 +1100, Bernardo <bernardo.bacic@pobox.com> said:
Bernardo> Hi Robert,
Bernardo> apologies for the late response, i came down with a cold and wasn't
Bernardo> checking my email;
No worries.
Bernardo> i have a quick and dirty test along these lines (+ include headers)
Bernardo> emulating what's happening when a lock is created/removed.
Bernardo> ,----
Bernardo> | int main()
Bernardo> | {
Bernardo> | const char buff[] = "abc";
Bernardo> |
Bernardo> | int fd = open( "another_test", O_RDWR|O_CREAT|O_EXCL|O_CLOEXEC, 0600);
Bernardo> | write( fd , buff, 3 );
Bernardo> | fchmod( fd, 0444 );
Bernardo> | close( fd );
Bernardo> | unlink( "another_test" );
Bernardo> | return 0;
Bernardo> | }
Bernardo> `----
Bernardo> as you would expect works fine here (at home) on ext4 file system;
Bernardo> will try this on work computer (most likely tomorrow) where VirtualBox
Bernardo> is installed, possibly tweak the file access flags and report the
Bernardo> results back;
Thanks. I might have a VirtualBox instance lying around, but itʼs
hosted on GNU/Linux, not Windows, so the behaviour is likely to be
different.
Bernardo> thanks for looking into this
Youʼre welcome.
Eli, if the results come back that using 0664 or similar on lockfiles
resolves this, would you be amenable to such a change?
Robert
next prev parent reply other threads:[~2019-10-27 15: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 [this message]
2019-10-27 15:52 ` Eli Zaretskii
2019-10-27 16:01 ` Robert Pluim
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
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=m2y2x6p5gh.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=37884@debbugs.gnu.org \
--cc=bernardo.bacic@pobox.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).