access.2: Note that access() may also fail for FUSE

Since in some cases (e.g. libguestfs's guestmount) it also has the
semantics where files can appear owned by root, but are actually
mutable by the user, despite what one might infer from the Unix
permissions.

Signed-off-by: Colin Walters <walters@verbum.org>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

man2/access.2

@@ -40,7 +40,8 @@
 .\" Modified 2004-06-23 by Michael Kerrisk
 .\" 2007-06-10, mtk, various parts rewritten, and added BUGS section.
 .\"
-.TH ACCESS 2 2010-10-24 "Linux" "Linux Programmer's Manual"
+.TH ACCESS 2 2013-02-28
+inux" "Linux Programmer's Manual"
 .SH NAME
 access \- check real user's permissions for a file
 .SH SYNOPSIS
@@ -85,7 +86,7 @@ then an
 .B X_OK
 check is successful for a regular file if execute permission
 is enabled for any of the file owner, group, or other.
-.SH RETURN VALUE
+.SH "RETURN VALUE"
 On success (all requested permissions granted), zero is returned.
 On error (at least one bit in
 .I mode
@@ -145,7 +146,7 @@ Insufficient kernel memory was available.
 .B ETXTBSY
 Write access was requested to an executable which is being
 executed.
-.SH CONFORMING TO
+.SH "CONFORMING TO"
 SVr4, 4.3BSD, POSIX.1-2001.
 .SH NOTES
 .PP
@@ -204,6 +205,7 @@ call will still fail.
 may not work correctly on NFS file systems with UID mapping enabled,
 because UID mapping is done on the server and hidden from the client,
 which checks permissions.
+Similar problems can occur to FUSE mounts.
 .SH BUGS
 In kernel 2.4 (and earlier) there is some strangeness in the handling of
 .B X_OK
@@ -238,7 +240,7 @@ the underlying file system.
 Since kernel 2.6.20,
 .BR access ()
 honors this flag.
-.SH SEE ALSO
+.SH "SEE ALSO"
 .BR chmod (2),
 .BR chown (2),
 .BR faccessat (2),