| access.2 (178245) | access.2 (208027) |
|---|---|
| 1.\" Copyright (c) 1980, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 12 unchanged lines hidden (view full) --- 21.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 22.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 23.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 24.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 25.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 26.\" SUCH DAMAGE. 27.\" 28.\" @(#)access.2 8.2 (Berkeley) 4/1/94 | 1.\" Copyright (c) 1980, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 12 unchanged lines hidden (view full) --- 21.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 22.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 23.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 24.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 25.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 26.\" SUCH DAMAGE. 27.\" 28.\" @(#)access.2 8.2 (Berkeley) 4/1/94 |
| 29.\" $FreeBSD: head/lib/libc/sys/access.2 178245 2008-04-16 13:03:12Z kib $ | 29.\" $FreeBSD: head/lib/libc/sys/access.2 208027 2010-05-13 12:07:55Z uqs $ |
| 30.\" 31.Dd April 10, 2008 32.Dt ACCESS 2 33.Os 34.Sh NAME 35.Nm access , 36.Nm eaccess , 37.Nm faccessat --- 145 unchanged lines hidden (view full) --- 183The 184.Fa path 185argument is not an absolute path and 186.Fa fd 187is neither 188.Dv AT_FDCWD 189nor a file descriptor associated with a directory. 190.El | 30.\" 31.Dd April 10, 2008 32.Dt ACCESS 2 33.Os 34.Sh NAME 35.Nm access , 36.Nm eaccess , 37.Nm faccessat --- 145 unchanged lines hidden (view full) --- 183The 184.Fa path 185argument is not an absolute path and 186.Fa fd 187is neither 188.Dv AT_FDCWD 189nor a file descriptor associated with a directory. 190.El |
| 191.Sh SEE ALSO 192.Xr chmod 2 , 193.Xr intro 2 , 194.Xr stat 2 195.Sh STANDARDS 196The 197.Fn access 198system call is expected to conform to 199.St -p1003.1-90 . 200The 201.Fn faccessat 202system call follows The Open Group Extended API Set 2 specification. 203.Sh HISTORY 204The 205.Fn access 206function appeared in 207.At v7 . 208The 209.Fn faccessat 210system call appeared in 211.Fx 8.0 . |
|
| 191.Sh SECURITY CONSIDERATIONS 192The 193.Fn access 194system call 195is a potential security hole due to race conditions and 196should never be used. 197Set-user-ID and set-group-ID applications should restore the 198effective user or group ID, --- 8 unchanged lines hidden (view full) --- 207.Fn access 208remains useful for providing clues to users as to whether operations 209make sense for particular filesystem objects (e.g. 'delete' menu 210item only highlighted in a writable folder ... avoiding interpretation 211of the st_mode bits that the application might not understand -- 212e.g. in the case of AFS). 213It also allows a cheaper file existence test than 214.Xr stat 2 . | 212.Sh SECURITY CONSIDERATIONS 213The 214.Fn access 215system call 216is a potential security hole due to race conditions and 217should never be used. 218Set-user-ID and set-group-ID applications should restore the 219effective user or group ID, --- 8 unchanged lines hidden (view full) --- 228.Fn access 229remains useful for providing clues to users as to whether operations 230make sense for particular filesystem objects (e.g. 'delete' menu 231item only highlighted in a writable folder ... avoiding interpretation 232of the st_mode bits that the application might not understand -- 233e.g. in the case of AFS). 234It also allows a cheaper file existence test than 235.Xr stat 2 . |
| 215.Sh SEE ALSO 216.Xr chmod 2 , 217.Xr intro 2 , 218.Xr stat 2 219.Sh STANDARDS 220The 221.Fn access 222system call is expected to conform to 223.St -p1003.1-90 . 224The 225.Fn faccessat 226system call follows The Open Group Extended API Set 2 specification. 227.Sh HISTORY 228The 229.Fn access 230function appeared in 231.At v7 . 232The 233.Fn faccessat 234system call appeared in 235.Fx 8.0 . | |