Minor wording fixes

This commit is contained in:
Michael Kerrisk 2007-05-30 15:43:44 +00:00
parent 0b0bb11aeb
commit dfaae36266
1 changed files with 6 additions and 6 deletions

View File

@ -49,7 +49,7 @@ access \- check user's permissions for a file
.fi
.SH DESCRIPTION
.BR access ()
checks whether the process would be allowed to read,
checks whether the calling process would be allowed to read,
write or test for existence of the file (or other file system
object) whose name is
.IR pathname .
@ -74,7 +74,7 @@ occurring in the path to the file, as given in
and on the permissions of directories and files referred to by symbolic
links encountered on the way.
The check is done with the process's
The check is done with the calling process's
.I real
UID and GID, rather than with the effective IDs as is done when
actually attempting an operation.
@ -90,7 +90,7 @@ Similarly, a DOS file may be found to be "executable," but the
.BR execve (2)
call will still fail.
If the process has appropriate privileges, an implementation may
If the calling process has appropriate privileges, an implementation may
indicate success for
.B X_OK
even if none of the execute file permission bits are set.
@ -107,7 +107,7 @@ is set appropriately.
shall fail if:
.TP
.B EACCES
The requested access would be denied to the file or search permission
The requested access would be denied to the file, or search permission
is denied for one of the directories in the path prefix of
.IR pathname .
(See also
@ -169,8 +169,8 @@ which checks permissions.
.BR Warning:
Using
.BR access ()
to check if a user is authorized to e.g. open a file before actually
doing so using
to check if a user is authorized to, for example,
open a file before actually doing so using
.BR open (2)
creates a security hole, because the user might exploit the short time
interval between checking and opening the file to manipulate it.