|author||Rich Felker <email@example.com>||2015-02-03 00:31:35 -0500|
|committer||Rich Felker <firstname.lastname@example.org>||2015-02-03 00:31:35 -0500|
make execvp continue PATH search on EACCES rather than issuing an errror
the specification for execvp itself is unclear as to whether encountering a file that cannot be executed due to EACCES during the PATH search is a mandatory error condition; however, XBD 8.3's specification of the PATH environment variable clarifies that the search continues until a file with "appropriate execution permissions" is found. since it seems undesirable/erroneous to report ENOENT rather than EACCES when an early path element has a non-executable file and all later path elements lack any file by the requested name, the new code stores a flag indicating that EACCES was seen and sets errno back to EACCES in this case.
Diffstat (limited to 'src/stat/fchmodat.c')
0 files changed, 0 insertions, 0 deletions