t_sndrel - initiate an orderly release
int t_sndrel (int fd);
This function is used to initiate an orderly release of a transport
connection and indicates to the transport provider that the transport
user has no more data to send. fd identifies the local transport
endpoint where the connection exists. After issuing t_sndrel, the user
may not send any more data over the connection. However, a user may
continue to receive data if an orderly release indication has not been
This function is an optional service of the transport provider, and is
only supported if the transport provider returned service type T_COTS_ORD
on t_open or t_getinfo.
If t_sndrel is issued from an invalid state, the provider will generate
an EPROTO protocol error; however, this error may not occur until a
subsequent reference to the transport endpoint.
This function resides within both the X/Open compliant libxnet and the
SVR4 compliant libnsl Network Services libraries. Network Services
applications which require X/Open compliance must link-load with -lxnet.
Network Services applications which require SVR4 compliance must linkload
On failure, t_errno may be set to one of the following:
TBADF The specified file descriptor does not refer to a
TFLOW O_NDELAY or O_NONBLOCK was set, but the flow control
mechanism prevented the transport provider from
accepting the function at this time.
TLOOK If _XOPEN_SOURCE is defined and an asynchronous event
has occurred on this transport endpoint which
requires immediate attention, then this t_errno is
TNOTSUPPORT This function is not supported by the underlying
TOUTSTATE If _XOPEN_SOURCE is defined and t_sndrel() is issued
in the wrong sequence on the transport endpoint
referenced by fd, the TOUTSTATE error value is
returned within the variable t_errno.
TSYSERR A system error has occurred during execution of this
t_getinfo(3N), t_open(3N), t_rcvrel(3N)
t_sndrel returns 0 on success and -1 on failure and t_errno is set to
indicate the error.
PPPPaaaaggggeeee 2222 [ Back ]