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

System Functions (s and S) spt_connectx(2)

The pathconf( ) function can be called to obtain the applicable limits.

[ENETDOWN]

The local interface used to reach the destination is down.

[ENETUNREACH]

No route to the network or host is present.

[ENOBUFS] There was not enough buffer space available to complete the call. A retry at a

later time may succeed.

[ENOENT] The socket is in the AF_UNIX domain and one of the following conditions

exists:

• A component of the pathname speciﬁed in the sockaddr structure does

not name an existing ﬁle.

• The sockaddr structure speciﬁes an empty string as a pathname.

[ENOMEM] Required memory resources were not available. A retry at a later time might

succeed.

[ENOTDIR] The socket is in the AF_UNIX domain and a component of the pathname

speciﬁed in the sockaddr structure is not a directory.

[ENOTSOCK] The socket parameter does not refer to a socket.

[EPROTOTYPE]

The speciﬁed address has a different type than that of the socket bound to the

speciﬁed peer address.

[ETIMEDOUT]

The attempt to connect timed out during connection establishment.

RELATED INFORMATION

Functions: accept(2), bind(2), connect(2), getsockname(2), select(2), send(2), sendmsg(2),

sendto(2), socket(2), spt_connect(2), spt_sendx(2), spt_sendmsgx(2), spt_sendtox(2).

STANDARDS CONFORMANCE

This function is an extension to the UNIX 98 speciﬁcation. 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 ﬁle spthread.h is an HP exception to the POSIX standard.

The XPG4 speciﬁcation allows certain behaviors of connect() to be implementer-deﬁned. See

the connect(2) reference page either online or in the Open System Services System Calls Refer-

ence Manual for an indication of the HP implementation behaviors.

527186-005 Hewlett-Packard Company 7−103