]> git.saurik.com Git - apple/xnu.git/blame - bsd/man/man2/access.2
xnu-4903.270.47.tar.gz
[apple/xnu.git] / bsd / man / man2 / access.2
CommitLineData
9bccf70c
A
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.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\" notice, this list of conditions and the following disclaimer in the
11.\" documentation and/or other materials provided with the distribution.
9bccf70c
A
12.\" 4. Neither the name of the University nor the names of its contributors
13.\" may be used to endorse or promote products derived from this software
14.\" without specific prior written permission.
15.\"
16.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
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
39037602 29.\" $FreeBSD$
9bccf70c 30.\"
39037602 31.Dd September 15, 2014
9bccf70c 32.Dt ACCESS 2
39037602 33.Os
9bccf70c 34.Sh NAME
fe8ab488
A
35.Nm access ,
36.Nm faccessat
39037602 37.Nd check accessibility of a file
9bccf70c 38.Sh SYNOPSIS
39037602 39.In unistd.h
9bccf70c 40.Ft int
39037602 41.Fn access "const char *path" "int mode"
fe8ab488
A
42.Ft int
43.Fn faccessat "int fd" "const char *path" "int mode" "int flag"
9bccf70c
A
44.Sh DESCRIPTION
45The
46.Fn access
39037602 47system call checks the accessibility of the
9bccf70c 48file named by
39037602 49the
9bccf70c 50.Fa path
39037602 51argument
9bccf70c 52for the access permissions indicated by
39037602
A
53the
54.Fa mode
55argument.
9bccf70c 56The value of
39037602
A
57.Fa mode
58is either the bitwise-inclusive OR of the access permissions to be
9bccf70c 59checked
39037602 60.Dv ( R_OK
9bccf70c
A
61for read permission,
62.Dv W_OK
39037602 63for write permission, and
9bccf70c 64.Dv X_OK
39037602
A
65for execute/search permission),
66or the existence test
67.Pq Dv F_OK .
68.Pp
69For additional information, see the
70.Sx "File Access Permission"
71section of
72.Xr intro 2 .
9bccf70c 73.Pp
39037602
A
74The
75.Fn access
76system call uses
77the real user ID in place of the effective user ID,
78the real group ID in place of the effective group ID,
79and the rest of the group access list.
9bccf70c 80.Pp
fe8ab488
A
81The
82.Fn faccessat
83system call is equivalent to
84.Fn access
85except in the case where
86.Fa path
87specifies a relative path.
88In this case the file whose accessibility is to be determined is
89located relative to the directory associated with the file descriptor
90.Fa fd
91instead of the current working directory.
92If
93.Fn faccessat
94is passed the special value
95.Dv AT_FDCWD
96in the
97.Fa fd
98parameter, the current working directory is used and the behavior is
99identical to a call to
100.Fn access .
101Values for
102.Fa flag
103are constructed by a bitwise-inclusive OR of flags from the following
104list, defined in
105.In fcntl.h :
106.Bl -tag -width indent
107.It Dv AT_EACCESS
108The checks for accessibility are performed using the effective user and group
109IDs instead of the real user and group ID as required in a call to
110.Fn access .
111.El
112.Pp
9bccf70c
A
113Even if a process has appropriate privileges and indicates success for
114.Dv X_OK ,
115the file may not actually have execute permission bits set.
116Likewise for
117.Dv R_OK
118and
119.Dv W_OK .
120.Sh RETURN VALUES
39037602 121.Rv -std
9bccf70c 122.Sh ERRORS
39037602
A
123.Fn access
124or
125.Fn faccessat
126will fail if:
9bccf70c 127.Bl -tag -width Er
2d21ac55 128.It Bq Er EINVAL
39037602
A
129The value of the
130.Fa mode
131argument is invalid.
132.It Bq Er ENOTDIR
133A component of the path prefix is not a directory.
9bccf70c
A
134.It Bq Er ENAMETOOLONG
135A component of a pathname exceeded
136.Dv {NAME_MAX}
137characters, or an entire path name exceeded
138.Dv {PATH_MAX}
139characters.
140.It Bq Er ENOENT
141The named file does not exist.
39037602
A
142.It Bq Er ELOOP
143Too many symbolic links were encountered in translating the pathname.
9bccf70c
A
144.It Bq Er EROFS
145Write access is requested for a file on a read-only file system.
146.It Bq Er ETXTBSY
147Write access is requested for a pure procedure (shared text)
39037602
A
148file presently being executed.
149.It Bq Er EACCES
150Permission bits of the file mode do not permit the requested
151access, or search permission is denied on a component of the
152path prefix.
153.It Bq Er EFAULT
154The
155.Fa path
156argument
157points outside the process's allocated address space.
158.It Bq Er EIO
159An I/O error occurred while reading from or writing to the file system.
9bccf70c 160.El
fe8ab488
A
161.Pp
162Also, the
163.Fn faccessat
164system call may fail if:
165.Bl -tag -width Er
166.It Bq Er EBADF
167The
168.Fa path
169argument does not specify an absolute path and the
170.Fa fd
171argument is
172neither
173.Dv AT_FDCWD
174nor a valid file descriptor.
175.It Bq Er EINVAL
176The value of the
177.Fa flag
178argument is not valid.
179.It Bq Er ENOTDIR
180The
181.Fa path
182argument is not an absolute path and
183.Fa fd
184is neither
185.Dv AT_FDCWD
186nor a file descriptor associated with a directory.
187.El
9bccf70c
A
188.Sh SEE ALSO
189.Xr chmod 2 ,
39037602 190.Xr intro 2 ,
9bccf70c
A
191.Xr stat 2
192.Sh STANDARDS
193The
194.Fn access
39037602 195system call is expected to conform to
9bccf70c 196.St -p1003.1-90 .
fe8ab488
A
197The
198.Fn faccessat
199system call is expected to conform to POSIX.1-2008 .
39037602
A
200.Sh HISTORY
201The
202.Fn access
203function appeared in
204.At v7 .
205.Sh SECURITY CONSIDERATIONS
206The result of
207.Fn access
208should not be used to make an actual access control decision, since its
209response, even if correct at the moment it is formed, may be outdated at the
210time you act on it.
211.Fn access
212results should only be used to pre-flight, such as when configuring user
213interface elements or for optimization purposes. The actual access control
214decision should be made by attempting to execute the relevant system call while
215holding the applicable credentials, and properly handling any resulting errors;
216and this must be done even though
217.Fn access
218may have predicted success.
219.Pp
220Additionally, set-user-ID and set-group-ID applications should restore the
221effective user or group ID,
222and perform actions directly rather than use
fe8ab488 223.Fn access
39037602 224to simulate access checks for the real user or group ID.