.\" Modified 2004-06-23 by Michael Kerrisk
.\" 2007-06-10, mtk, various parts rewritten, and added BUGS section.
.\"
-.TH ACCESS 2 2014-02-21 "Linux" "Linux Programmer's Manual"
+.TH ACCESS 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
access, faccessat \- check user's permissions for a file
.SH SYNOPSIS
.B X_OK
check is successful for a regular file if execute permission
is enabled for any of the file owner, group, or other.
-.SS faccessat ()
+.SS faccessat()
The
.BR faccessat ()
system call operates in exactly the same way as
Similar problems can occur to FUSE mounts.
.\"
.\"
-.SS faccessat ()
+.SS C library/kernel ABI differences
The raw
.BR faccessat ()
system call takes only the first three arguments.
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
.BR credentials (7),
.BR path_resolution (7),
.BR symlink (7)
+.SH COLOPHON
+This page is part of release 3.79 of the Linux
+.I man-pages
+project.
+A description of the project,
+information about reporting bugs,
+and the latest version of this page,
+can be found at
+\%http://www.kernel.org/doc/man\-pages/.