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

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

Contents


t_sync(3N)							    t_sync(3N)


NAME    [Toc]    [Back]

     t_sync - synchronize transport library

SYNOPSIS    [Toc]    [Back]

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

     int t_sync	(int fd);

DESCRIPTION    [Toc]    [Back]

     For the transport endpoint	specified by fd, t_sync	synchronizes the data
     structures	managed	by the transport library with information from the
     underlying	transport provider.  In	doing so, it can convert a raw file
     descriptor	[obtained via open(2), dup(2), or as a result of a fork(2) and
     exec(2)] to an initialized	transport endpoint, assuming that file
     descriptor	referenced a transport provider.  This function	also allows
     two cooperating processes to synchronize their interaction	with a
     transport provider.

     For example, if a process forks a new process and issues an exec, the new
     process must issue	a t_sync to build the private library data structure
     associated	with a transport endpoint and to synchronize the data
     structure with the	relevant provider information.

     It	is important to	remember that the transport provider treats all	users
     of	a transport endpoint as	a single user.	If multiple processes are
     using the same endpoint, they should coordinate their activities so as
     not to violate the	state of the provider.	t_sync returns the current
     state of the provider to the user,	thereby	enabling the user to verify
     the state before taking further action.  This coordination	is only	valid
     among cooperating processes; it is	possible that a	process	or an incoming
     event could change	the provider's state after a t_sync is issued.

     If	the provider is	undergoing a state transition when t_sync is called,
     the function will fail.

     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.






									Page 1






t_sync(3N)							    t_sync(3N)



     TSTATECHNG		The transport provider is undergoing a state change.

     TSYSERR		A system error has occurred during execution of	this
			function.

SEE ALSO    [Toc]    [Back]

      
      
     dup(2), exec(2), fork(2), open(2)

DIAGNOSTICS    [Toc]    [Back]

     t_sync returns the	state of the transport provider	on successful
     completion	and -1 on failure and t_errno is set to	indicate the error.
     The state returned	may be one of the following:

     T_UNBND		unbound

     T_IDLE		idle

     T_OUTCON		outgoing connection pending

     T_INCON		incoming connection pending

     T_DATAXFER		data transfer

     T_OUTREL		outgoing orderly release (waiting for an orderly
			release	indication)

     T_INREL		incoming orderly release (waiting for an orderly
			release	request)


									PPPPaaaaggggeeee 2222
[ Back ]
 Similar pages
Name OS Title
named.reload FreeBSD cause the name server to synchronize its database
msync FreeBSD synchronize a mapped region
fdatasync NetBSD synchronize the data of a file
msync OpenBSD synchronize a mapped region
msync Tru64 Synchronize a mapped file
msync NetBSD synchronize a mapped region
sync HP-UX synchronize file systems
msync Linux synchronize a file with a memory map
msync IRIX synchronize memory with physical storage
glxjoinswapgroupsgix IRIX synchronize buffer swaps with other drawables
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service