Displaying 3 results from an estimated 3 matches for "nonexecut".
Did you mean:
nonexact
2008 Jul 06
1
Handful of files are giving me error 13, directory executable bit issue
I am getting a handful of these errors, and I am not sure why. The
directories in question have rights like this:
drw-r--r-- 2 osstbb osstbb 42 2008-05-02 00:04 12981826/
As root, why would it matter if it has executability? I can read it
just fine on the server.
Or is it an issue when it tries to create it on the -client- ? Is
there a way to fix this? I can chmod 0755 the dirs on the server
2019 Jan 25
0
[klibc:update-dash] [BUILTIN] Fix "test -x" as root on FreeBSD 8
...s, POSIX unfortunately also allows access() and
faccessat() to return success for X_OK if the current process is
privileged, even when the above condition is not fulfilled and actual
execution would fail. On the affected platforms, "test -x <path>" as
root started returning true on nonexecutable files when dash switched
from its own emulation to the true faccessat in v0.5.7~54
(2010-04-02).
Work around this by checking the permissions bits when mode == X_OK
and geteuid() == 0 on such platforms.
Unfortunately the behavior seems to vary from one kernel version to
another, so we cannot...
2020 Mar 28
0
[klibc:update-dash] dash: [BUILTIN] Fix "test -x" as root on FreeBSD 8
...s, POSIX unfortunately also allows access() and
faccessat() to return success for X_OK if the current process is
privileged, even when the above condition is not fulfilled and actual
execution would fail. On the affected platforms, "test -x <path>" as
root started returning true on nonexecutable files when dash switched
from its own emulation to the true faccessat in v0.5.7~54
(2010-04-02).
Work around this by checking the permissions bits when mode == X_OK
and geteuid() == 0 on such platforms.
Unfortunately the behavior seems to vary from one kernel version to
another, so we cannot...