From 2faeeff4c9bb77cca44a977d96c1a9fc7af8d8a3 Mon Sep 17 00:00:00 2001 From: Ruslan Ermilov Date: Wed, 18 Dec 2002 09:22:32 +0000 Subject: mdoc(7) police: Tidy up the syscall language. Stop calling system calls "function calls". Use "The .Fn system call" a-la "The .Nm utility". When referring to a non-BSD implementation in the HISTORY section, call syscall a function, to be safe. --- lib/libc/sys/access.2 | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) (limited to 'lib/libc/sys/access.2') diff --git a/lib/libc/sys/access.2 b/lib/libc/sys/access.2 index 5d912b864eb3..0d3611a742c0 100644 --- a/lib/libc/sys/access.2 +++ b/lib/libc/sys/access.2 @@ -51,7 +51,7 @@ The .Fn access and .Fn eaccess -functions check the accessibility of the +system calls check the accessibility of the file named by the .Fa path @@ -80,12 +80,12 @@ section of .Pp The .Fn eaccess -call uses +system call uses the effective user ID and the group access list to authorize the request; the .Fn access -call uses +system call uses the real user ID in place of the effective user ID, the real group ID in place of the effective group ID, and the rest of the group access list. @@ -130,7 +130,7 @@ An I/O error occurred while reading from or writing to the file system. .Sh SECURITY CONSIDERATIONS The .Fn access -call +system call is a potential security hole due to race conditions and should never be used. Set-user-ID and set-group-ID applications should restore the @@ -140,7 +140,7 @@ and perform actions directly rather than use to simulate access checks for the real user or group ID. The .Fn eaccess -call +system call likewise may be subject to races if used inappropriately. .Sh SEE ALSO .Xr chmod 2 , @@ -149,10 +149,10 @@ likewise may be subject to races if used inappropriately. .Sh STANDARDS The .Fn access -function call is expected to conform to +system call is expected to conform to .St -p1003.1-90 . .Sh HISTORY -An +The .Fn access -function call appeared in +function appeared in .At v7 . -- cgit v1.3