*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->IRIX man pages -> t_sndrel (3n)              
Title
Content
Arch
Section
 

Contents


t_sndrel(3N)							  t_sndrel(3N)


NAME    [Toc]    [Back]

     t_sndrel -	initiate an orderly release

SYNOPSIS    [Toc]    [Back]

     #ifdef _XOPEN_SOURCE
     #include <xti.h>
     #else
     #include <tiuser.h>
     #endif

     int t_sndrel (int fd);

DESCRIPTION    [Toc]    [Back]

     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
     received.

     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
 with -lnsl.

     On	failure, t_errno may be	set to one of the following:

     TBADF		 The specified file descriptor does not	refer to a
			 transport endpoint.

     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
			 passed	back.

     TNOTSUPPORT	 This function is not supported	by the underlying
			 transport provider.




									Page 1






t_sndrel(3N)							  t_sndrel(3N)



     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
			 function.

SEE ALSO    [Toc]    [Back]

      
      
     t_getinfo(3N), t_open(3N),	t_rcvrel(3N)

DIAGNOSTICS    [Toc]    [Back]

     t_sndrel returns 0	on success and -1 on failure and t_errno is set	to
     indicate the error.


									PPPPaaaaggggeeee 2222
[ Back ]
 Similar pages
Name OS Title
t_sndrel Tru64 Initiate an endpoint connect orderly release
t_sndreldata Tru64 Initiate or respond to an orderly release with user data
t_sysconf Tru64 Initiate or respond to an orderly release with user data
t_rcvrel IRIX acknowledge receipt of an orderly release indication
t_rcvrel Tru64 Acknowledge receipt of an orderly release indication
t_rcvrel HP-UX acknowledge receipt of an orderly release indication at a transport endpoint
t_rcvreldata Tru64 Receive an orderly release indication or confirmation containing user data
DtSearchExit HP-UX Perform orderly shutdown of search engine
pam_start FreeBSD initiate a PAM transaction
physio OpenBSD initiate I/O on raw devices
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service