Home
Search all pages
Subjects
By activity
Professions, Sciences, Humanities, Business, ...
User Interface
Text-based, GUI, Audio, Video, Keyboards, Mouse, Images,...
Text Strings
Conversions, tests, processing, manipulation,...
Math
Integer, Floating point, Matrix, Statistics, Boolean, ...
Processing
Algorithms, Memory, Process control, Debugging, ...
Stored Data
Data storage, Integrity, Encryption, Compression, ...
Communications
Networks, protocols, Interprocess, Remote, Client Server, ...
Hard World Timing, Calendar and Clock, Audio, Video, Printer, Controls...
File System
Management, Filtering, File & Directory access, Viewers, ...
|
|
|
RocketLink!--> Man page versions:
OpenBSD
FreeBSD
NetBSD
RedHat
Solaris
Others
ACCESS(2) OpenBSD Programmer's Manual ACCESS(2)
NAME
access - check access permissions of a file or pathname
SYNOPSIS
#include <unistd.h>
int
access(const char *path, int mode);
DESCRIPTION
The access() function checks the accessibility of the file named by path
for the access permissions indicated by mode. The value of mode is the
bitwise inclusive OR of the access permissions to be checked (R_OK for
read permission, W_OK for write permission and X_OK for execute/search
permission) or the existence test, F_OK. All components of the pathname
path are checked for access permissions (including F_OK).
The real user ID is used in place of the effective user ID and the real
group access list (including the real group ID) are used in place of the
effective ID for verifying permission.
Even if a process has appropriate privileges and indicates success for
X_OK, the file may not actually have execute permission bits set. Like-
wise for R_OK and W_OK.
RETURN VALUES
If path cannot be found or if any of the desired access modes would not
be granted, then a -1 value is returned; otherwise a 0 value is returned.
ERRORS
Access to the file is denied if:
[ENOTDIR] A component of the path prefix is not a directory.
[ENAMETOOLONG]
A component of a pathname exceeded {NAME_MAX} characters,
or an entire path name exceeded {PATH_MAX} characters.
[ENOENT] The named file does not exist.
[ELOOP] Too many symbolic links were encountered in translating the
pathname.
[EROFS] Write access is requested for a file on a read-only file
system.
[ETXTBSY] Write access is requested for a pure procedure (shared
text) file presently being executed.
[EACCES] Permission bits of the file mode do not permit the request-
ed access, or search permission is denied on a component of
the path prefix. The owner of a file has permission
checked with respect to the ``owner'' read, write, and exe-
cute mode bits, members of the file's group other than the
owner have permission checked with respect to the ``group''
mode bits, and all others have permissions checked with re-
spect to the ``other'' mode bits.
[EFAULT] path points outside the process's allocated address space.
[EIO] An I/O error occurred while reading from or writing to the
file system.
[EINVAL] An invalid value was specified for mode.
SEE ALSO
chmod(2), stat(2)
STANDARDS
The access() function conforms to IEEE Std1003.1-1990 (``POSIX'').
CAVEAT
access() is a potential security hole and should never be used.
OpenBSD 2.6 April 1, 1994 2
Source: OpenBSD 2.6 man pages. Copyright: Portions are copyrighted by BERKELEY SOFTWARE DESIGN, INC., The Regents of the University of California, Massachusetts Institute of Technology, Free Software Foundation, FreeBSD Inc., and others. |
(Corrections, notes, and links courtesy of RocketAware.com)
Up to: File Access Limits - Limiting access to files (permissions, locking, et al)
Up to: File Information - Obtaining file information (status, configuration, et al)
RocketLink!--> Man page versions:
OpenBSD
FreeBSD
NetBSD
RedHat
Solaris
Others
Rapid-Links:
Search | About | Comments | Submit Path: RocketAware > man pages >
access.2/
RocketAware.com is a service of Mib Software Copyright 1999, Forrest J. Cavalier III. All Rights Reserved. We welcome submissions and comments
|