From 1a7d4eb74cfca77932cacefd2904a3bde308637f Mon Sep 17 00:00:00 2001 From: "J. Bruce Fields" Date: Wed, 11 Sep 2013 16:22:11 -0400 Subject: [PATCH] access.2: Fix outdated NFS information Note that NFS versions since version 3 support an "access" call so that the client doesn't have to guess permissions or ID mapping on its own. (See RFC 1813 sections 1.7 and 3.3.4.) Signed-off-by: J. Bruce Fields Signed-off-by: Michael Kerrisk --- man2/access.2 | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/man2/access.2 b/man2/access.2 index 6df68de57..665758d1f 100644 --- a/man2/access.2 +++ b/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 @@ -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 filesystems 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