Open System Services System Calls Reference Manual (G06.29+, H06.08+, J06.03+)

System Functions (s and S) spt_acceptx(2)
[EFAULT] A user-supplied memory buffer cannot be accessed or written.
[EINTR] The function call was interrupted by a signal that was caught before a valid con-
nection arrived.
[EINVAL] The socket is not accepting connections.
[EMFILE] No more file descriptors are available for this process.
[ENFILE] The maximum number of file descriptors for this processor are already open.
[ENOBUFS] Not enough buffer space was available to complete the call. A retry at a later
time might succeed.
[ENOMEM] Required memory resources were not available. A retry at a later time might
succeed.
[ENOTSOCK] The socket parameter does not specify a socket.
[EOPNOTSUPP]
The socket type of the specified socket does not support accepting connections.
[EWOULDBLOCK]
The socket’s file descriptor is marked nonblocking (O_NONBLOCK is set) and
no connections are present to be accepted.
RELATED INFORMATION
Functions: accept(2), bind(2), connect(2), fcntl(2), listen(2), socket(2), spt_accept(2),
pthread_kill(2).
STANDARDS CONFORMANCE
This function is an extension to the UNIX 98 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.
The XPG4 specification allows certain behaviors of accept() to be implementer-defined. For an
indication of the HP implementation behaviors, see the accept(2) reference page either online or
in the Open System Services System Calls Reference Manual.
527186-023 Hewlett-Packard Company 7−133