(split) LDP: Update original to LDP v3.54

[linuxjm/LDP_man-pages.git] / original / man2 / access.2

diff --git a/original/man2/access.2 b/original/man2/access.2
index d550b66..665758d 100644 (file)
--- a/original/man2/access.2
+++ b/original/man2/access.2
@@ -40,7 +40,7 @@
 .\" Modified 2004-06-23 by Michael Kerrisk
 .\" 2007-06-10, mtk, various parts rewritten, and added BUGS section.
 .\"
-.TH ACCESS 2 2013-04-16 "Linux" "Linux Programmer's Manual"
+.TH ACCESS 2 2013-09-13 "Linux" "Linux Programmer's Manual"
 .SH NAME
 access \- check real user's permissions for a file
 .SH SYNOPSIS
@@ -131,7 +131,7 @@ A component used as a directory in
 is not, in fact, a directory.
 .TP
 .B EROFS
-Write permission was requested for a file on a read-only file system.
+Write permission was requested for a file on a read-only filesystem.
 .PP
 .BR access ()
 may fail if:
@@ -209,9 +209,10 @@ Similarly, a DOS file may be found to be "executable," but the
 call will still fail.
 .PP
 .BR access ()
-may not work correctly on NFS file systems with UID mapping enabled,
+may not work correctly on NFSv2 filesystems with UID mapping enabled,
 because UID mapping is done on the server and hidden from the client,
-which checks permissions.
+which checks permissions.  (NFS versions 3 and higher perform the check on
+the server.)
 Similar problems can occur to FUSE mounts.
 .SH BUGS
 In kernel 2.4 (and earlier) there is some strangeness in the handling of
@@ -243,7 +244,7 @@ ignored the effect of the
 .B MS_NOEXEC
 flag if it was used to
 .BR mount (2)
-the underlying file system.
+the underlying filesystem.
 Since kernel 2.6.20,
 .BR access ()
 honors this flag.