A/UX® Programmer's Reference

access(2)
[ENOENT]
[ENOENT]
[EACCES]
[EROFS]
[ETXTBSY]
[EACCESS]
[EFAULT]
[EINVAL]
access(2)
Read, write, or execute (search) permission
is requested for a null pathname.
The named file does not exist.
Search permission is denied on a component
of the path prefix.
Write access is requested for a file on a
read-only file system.
Write access is requested for a pure procedure
(shared text) file that is being executed.
Note: If you are running network
file system (NFS) and you are accessing
a shared binary remotely,
it is possible that you will not get
this errno.
Permission bits of the file mode do not
permit the requested access.
The path points outside the allocated address
space for the process.
Value of amode is invalid.
The owner of a file has permission checked with respect to the
"owner" read, write, and execute mode bits. Members of the
file's group, other than the owner, have permissions checked with
respect to the "group" mode bits, and all others have permissions
checked with respect to the "other" mode bits.
The superuser is always granted execute permission even though
execute permission is meaningful only for directories and regular
files and even though exec requires that at least one execute
mode bit is set for the regular file to be executable.
Notice that only access bits are checked. A directory may be announced
as writable by access, but an attempt to open it for
writing will fail because writing into the directory structure itself
is not allowed, even though files may be created there. A file may
look executable, but exec will fail unless it is in the proper format.
February, 1990 2
Revision C