rpcregistry(3i) [debian man page]

RpcRegistry(3I) 					    InterViews Reference Manual 					   RpcRegistry(3I)

NAME

       RpcRegistry - name space for finding RPC services

SYNOPSIS

       #include <Dispatch/rpcregistry.h>

DESCRIPTION

       RpcRegistry provides a name space for finding RPC services based on the use of NFS filesystems among a group of hosts.  When an RPC service
       wishes to record its host name and port number, it will give the path of a file in which to store the information.  When a client wants	to
       find  the  RPC  service's  host name and port number, it will give the path of a file from which to read the information.  Usually the path
       will be the name of a file in the current working directory since different hosts may have different absolute pathnames for the	same  file
       in a NFS filesystem.  The RPC service's name space is the name space of the host's filesystem and the file's contents provides the informa-
       tion needed to open a connection to the RPC service.

PUBLIC OPERATIONS

       Each function is a static member function, which means a program can call it without having to instantiate  an  RpcRegistry  object.   Each
       function returns true if it succeeded or false if some error occurred.

       boolean record(const char* path, int port)
	      Record  the  RPC	service's  host name and port number in the given file.  If the file already exists, its previous contents will be
	      lost.

       boolean erase(const char* path)
	      Remove the file which stores the RPC service's host name and port number so that no more clients will be able  to  contact  the  RPC
	      service.

       boolean find(const char* path, char*& hostname, int& port)
	      Open  the  file  which stores the RPC service's host name and port number.  If the file does not exist, return failure silently.	If
	      the file does exist, read the RPC service's host name and port address from it.  If ``hostname'' is nil upon entry, it will  contain
	      the address of a dynamically allocated string upon exit (which must be freed by the caller).

SEE ALSO

       RpcService(3I)

InterViews							   27 March 1991						   RpcRegistry(3I)

rpcbind(1M)															       rpcbind(1M)

NAME

       rpcbind - universal addresses to RPC program number mapper

SYNOPSIS

DESCRIPTION

       is  a  server that converts RPC program numbers into universal addresses.  It must be running on the host to be able to make RPC calls on a
       server on that machine.

       When an RPC service is started, it tells the address at which it is listening, and the RPC program numbers it is prepared to serve.  When a
       client  wishes  to  make  an RPC call to a given program number, it first contacts on the server machine to determine the address where RPC
       requests should be sent.

       should be started before any other RPC service.	Normally, standard RPC servers are started by port monitors, so  must  be  started  before
       port monitors are invoked.

       When  is  started,  it  checks  that certain name-to-address translation calls function correctly.  If they fail, the network configuration
       databases may be corrupt.  Since RPC services cannot function correctly in this situation, reports the condition and terminates.

       can only be started by the super-user.

   Options
       recognizes the following options:

	      Run in debug mode.
			In this mode, will not fork when it starts, will print additional information during operation, and will abort on  certain
			errors.  With this option, the name-to-address translation consistency checks are shown in detail.

	      Do a warm start.
			If  aborts  or	terminates  on	or  it	will write the current list of registered services to and Starting with the option
			instructs it to look for these files and start operation with the registrations found in  them.   This	allows	to  resume
			operation without requiring all RPC services to be restarted.

WARNINGS

       Terminating with will prevent the warm-start files from being written.

       All  RPC  servers  must be restarted if the following occurs: crashes (or is killed with and is unable to to write the warm-start files; is
       started without the option after a graceful termination; or, the warm-start files are not found by

AUTHOR

       was developed by Sun Microsystems, Inc.

FILES

SEE ALSO

       rpcinfo(1M), rpcbind(3N).

																       rpcbind(1M)