Open System Services System Calls Reference Manual (G06.28+)

readdir_r(2) OSS System Calls Reference Manual
RETURN VALUES
Upon successful completion, the readdir_r() function returns the value 0 (zero). Otherwise, a
nonzero error number is returned, and errno is set to indicate the error. See the ERRORS sub-
section of this reference page for the possible values that can be returned.
ERRORS
If any of the following conditions occurs, the readdir_r() function sets errno to the correspond-
ing value:
[EBADF] The dirp parameter does not point to a valid directory structure open for reading.
[EFAULT] The dirp parameter does not point to a valid directory structure open for reading.
[EINVAL] Table overflow occurred after the last valid telldir() function call for a Guardian
disk volume or subvolume. Only the last 128 values returned by the telldir()
function can be saved in the table.
[EIO] An I/O error occurred during a read from the directory.
[ENETDOWN]
The dirp parameter specifies a directory on a remote HP NonStop server node
but communication with the remote node has been lost.
[ENOENT] An invalid position value was used in the previous call to the seekdir() function.
[ENOMEM] The system has insufficient resources to complete the request.
[ENOROOT] The root fileset (fileset 0) is not in the STARTED state.
[ENXIO] One of the following events occurred:
• A device was specified that does not exist, or a request was made beyond
the limits of the device.
• The fileset containing the requestor’s current working directory or root
directory is not mounted. This error can occur after failure and restart of
an OSS name server until the fileset has been repaired and remounted.
[EWRONGID] The call cannot be completed because an input/output process has failed or is in
the down state.
RELATED INFORMATION
Functions: closedir(3), mkdir(2), opendir(3), readdir(3), rewinddir(3), rmdir(2), seekdir(3),
telldir(3).
STANDARDS CONFORMANCE
This function is an extension to the UNIX98 specification. Interfaces documented on this refer-
ence page conform to the following industry standards:
• IEEE Std 1003.1c-1995, POSIX System Application Program Interface
The use of the header file spthread.h is an HP exception to the POSIX standard.
6−8 Hewlett-Packard Company 527186-005