access.2: Glibc falls back to using access() on kernels that lack faccessat()

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2014-05-16 11:09:45 +02:00
parent c71a9ed732
commit cf81f364e8
1 changed files with 18 additions and 0 deletions

View File

@ -336,6 +336,24 @@ flags are actually implemented within the glibc wrapper function for
If either of these flags is specified, then the wrapper function employs
.BR fstatat (2)
to determine access permissions.
.SS Glibc notes
On older kernels where
.BR faccessat ()
is unavailable (and when the
.B AT_EACCESS
and
.B AT_SYMLINK_NOFOLLOW
flags are not specified),
the glibc wrapper function falls back to the use of
.BR access ().
When
.I pathname
is a relative pathname,
glibc constructs a pathname based on the symbolic link in
.IR /proc/self/fd
that corresponds to the
.IR dirfd
argument.
.SH BUGS
In kernel 2.4 (and earlier) there is some strangeness in the handling of
.B X_OK