From: Alan Third <alan@idiocy.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 30350@debbugs.gnu.org, Paul Eggert <eggert@cs.ucla.edu>,
Sam Steingold <sds@podval.org>
Subject: bug#30350: 27.0.50; Newest master can't run processes on macOS
Date: Tue, 6 Feb 2018 22:44:55 +0000 [thread overview]
Message-ID: <20180206224455.GA97842@breton.holly.idiocy.org> (raw)
In-Reply-To: <CAArVCkTtExRqwFe0iw0NjqfQvc1K5httdYaNN=YZZVmQv=xiLA@mail.gmail.com>
On Tue, Feb 06, 2018 at 10:07:52PM +0000, Philipp Stephani wrote:
> However, when I change "file" to "/usr/bin/true" in the names list, the
> issue happens again (i.e. lstat and faccessat succeed for
> "/usr/bin/true/."). So this does appear to be a macOS bug, but it's not
> consistently reproducible.
Try setting the permissions of the test file to 500.
It looks like if the file is only readable and executable, then the
problem occurs, but if it’s writable it goes away.
That’s why we see it in places like /usr/bin where we don’t have write
permission, but can’t reproduce it in ~/ where we do.
--
Alan Third
next prev parent reply other threads:[~2018-02-06 22:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-04 20:15 bug#30350: 27.0.50; Newest master can't run processes on macOS Philipp
2018-02-04 20:20 ` Philipp Stephani
2018-02-04 21:06 ` Alan Third
2018-02-04 21:12 ` Alan Third
2018-02-04 21:28 ` Philipp Stephani
2018-02-04 22:49 ` Alan Third
2018-02-04 23:16 ` Philipp Stephani
2018-02-10 10:47 ` Eli Zaretskii
2018-02-04 20:24 ` Eli Zaretskii
2018-02-05 19:13 ` Paul Eggert
2018-02-05 19:18 ` Alan Third
2018-02-05 23:56 ` Paul Eggert
2018-02-06 0:26 ` Philipp Stephani
2018-02-06 0:36 ` Paul Eggert
2018-02-06 0:43 ` Philipp Stephani
2018-02-06 23:38 ` Paul Eggert
2018-02-06 8:28 ` Alan Third
2018-02-06 22:07 ` Philipp Stephani
2018-02-06 22:10 ` Philipp Stephani
2018-02-11 15:56 ` Philipp Stephani
2018-02-06 22:44 ` Alan Third [this message]
2018-02-06 22:53 ` Noam Postavsky
2018-02-11 16:01 ` Philipp Stephani
2018-02-11 21:15 ` Alan Third
2020-08-16 16:53 ` Lars Ingebrigtsen
2020-10-02 4:54 ` Lars Ingebrigtsen
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=20180206224455.GA97842@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=30350@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=p.stephani2@gmail.com \
--cc=sds@podval.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.