Index of Section 3 Manual Pages
| Interix / SUA | t_sndrel.3 | Interix / SUA |
t_sndrel(3) t_sndrel(3)
t_sndrel()
NAME
t_sndrel - initiate an orderly release
SYNOPSIS
#include
int t_sndrel(
int fd)
DESCRIPTION
For transport providers of type T_COTS_ORD, the t_sndrel(3) function is
used to initiate an orderly release of the outgoing direction of data
transfer and indicates to the transport provider that the transport user
has no more data to send.
Parameters Before call After call
fd x /
The argument fd identifies the local transport endpoint where the
connection exists. After calling 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 received. For transport
providers of types other than T_COTS_ORD, this function fails with error
[TNOTSUPPORT].
VALID STATES
T_DATAXFER,T_INREL
ERRORS
On failure, t_errno is set to one of the following:
[TBADF]
The specified file descriptor does not refer to a transport endpoint.
[TFLOW]
O_NONBLOCK was set, but the flow control mechanism prevented the
transport provider from accepting the function at this time.
[TLOOK]
An asynchronous event has occurred on this transport endpoint and
requires immediate attention.
[TNOTSUPPORT]
This function is not supported by the underlying transport provider.
[TOUTSTATE]
The communications endpoint referenced by fd is not in one of the
states in which a call to this function is valid.
[TPROTO]
This error indicates that a communication problem has been detected
between XTI and the transport provider for which there is no other
suitable XTI error (t_errno).
[TSYSERR]
A system error has occurred during execution of this function.
RETURN VALUE
Upon successful completion, a value of 0 is returned. Otherwise, a value
of -1 is returned and t_errno is set to indicate an error.
SEE ALSO
t_getinfo(3)
t_open(3)
t_rcvrel(3)
USAGE NOTES
The t_sndrel function is not thread safe.
The t_sndrel function is not async-signal safe.