x11r4 man page for t_close

Query: t_close

OS: x11r4

Section: 3nsl

Links: x11r4 man pages   all man pages

Forums: unix linux community   forum categories

Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar

t_close(3NSL)					       Networking Services Library Functions					     t_close(3NSL)

NAME
t_close - close a transport endpoint
SYNOPSIS
#include <xti.h> int t_close(int fd);
DESCRIPTION
This routine is part of the XTI interfaces which evolved from the TLI interfaces. XTI represents the future evolution of these interfaces. However, TLI interfaces are supported for compatibility. When using a TLI routine that has the same name as an XTI routine, the tiuser.h header file must be used. Refer to the TLI COMPATIBILITY section for a description of differences between the two interfaces. The t_close() function informs the transport provider that the user is finished with the transport endpoint specified by fd, and frees any local library resources associated with the endpoint. In addition, t_close() closes the file associated with the transport endpoint. The function t_close() should be called from the T_UNBND state. See t_getstate(3NSL). However, this function does not check state informa- tion, so it may be called from any state to close a transport endpoint. If this occurs, the local library resources associated with the endpoint will be freed automatically. In addition, close(2) will be issued for that file descriptor; if there are no other descriptors in this process or in another process which references the communication endpoint, any connection that may be associated with that endpoint is broken. The connection may be terminated in an orderly or abortive manner. A t_close() issued on a connection endpoint may cause data previously sent, or data not yet received, to be lost. It is the responsibility of the transport user to ensure that data is received by the remote peer.
RETURN VALUES
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.
VALID STATES
T_UNBND
ERRORS
On failure, t_errno is set to the following: TBADF The specified file descriptor does not refer to a transport endpoint. 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.
TLI COMPATIBILITY
The XTI and TLI interface definitions have common names but use different header files. This, and other semantic differences between the two interfaces are described in the subsections below. Interface Header The XTI interfaces use the header file, xti.h. TLI interfaces should not use this header. They should use the header: #include <tiuser.h> Error Description Values The t_errno value that can be set by the XTI interface and cannot be set by the TLI interface is: TPROTO
ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |MT Level |Safe | +-----------------------------+-----------------------------+
SEE ALSO
close(2), t_getstate(3NSL), t_open(3NSL), t_unbind(3NSL), attributes(5) SunOS 5.10 7 May 1998 t_close(3NSL)
Related Man Pages
t_close(3nsl) - minix
t_close(3nsl) - centos
t_close(3nsl) - opendarwin
t_close(3nsl) - debian
t_close(3nsl) - suse
Similar Topics in the Unix Linux Community
multiuser chat server closes when one client closes. code included
socket close hangs and CPU go to 100%
script does not close terminal after running
[Solved] Rsh does not close connection on exit
Cant close UNIX.com account