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)
Check Out this Related Man Page
rpcinfo(1M)rpcinfo(1M)NAME
rpcinfo - report RPC information
SYNOPSIS
[ ] [ ] [ host ]
[ host ]
host prognum [ versnum ]
[ ] host prognum [ versnum ]
[ ] host prognum [ versnum ]
[ ] host prognum [ versnum ]
prognum [ versnum ]
[ ] prognum versnum
[ ] prognum versnum
DESCRIPTION
makes an RPC call to an RPC server and reports what it finds.
In the first synopsis, lists all the registered RPC services with on host. If host is not specified, the local host is the default. If is
used, the information is displayed in a concise format.
In the second synopsis, lists all the RPC services registered with version 2. Also note that the format of the information is different in
the first and the second synopsis. This is because the second synopsis is an older protocol used to collect the information displayed
(version 2 of the protocol).
The third synopsis makes an RPC call to procedure of prognum and versnum on the specified host and reports whether a response was received.
transport is the transport which has to be used for contacting the given service. The remote address of the service is obtained by making
a call to the remote
The prognum argument is a number that represents an RPC program number (see rpc(4)).
If a versnum is specified, attempts to call that version of the specified prognum. Otherwise, attempts to find all the registered version
numbers for the specified prognum by calling version 0, which is presumed not to exist; if it does exist, attempts to obtain this informa-
tion by calling an extremely high version number instead, and attempts to call each registered version. Note that the version number is
required for and options.
The other ways of using are described in the section.
Options
Specify the transport on which the service is required.
If this option is not specified, uses the transport specified in the environment variable, or if that is unset or null, the
transport in the netconfig(4) database is used. This is a generic option, and can be used in conjunction with other options
as shown in the
Use serv_address as the (universal) address for the service on transport to ping procedure of the specified prognum and report
whether a response was received. The option is required with the option.
If versnum is not specified, tries to ping all available version numbers for that program number. This option avoids calls
to remote to find the address of the service. The serv_address is specified in universal address format of the given trans-
port.
Make an RPC broadcast to procedure
of the specified prognum and versnum and report all hosts that respond. If transport is specified, it broadcasts its
request only on the specified transport. If broadcasting is not supported by any transport, an error message is printed.
Use of broadcasting should be limited because of the potential for adverse effect on other systems.
Delete registration for the
RPC service of the specified prognum and versnum. If transport is specified, unregister the service on only that transport,
otherwise unregister the service on all the transports on which it was registered. Only the owner of a service can delete a
registration, except the super-user who can delete any service.
Display a list of entries with a given
prognum and versnum on the specified host. Entries are returned for all transports in the same protocol family as that used
to contact the remote
Display a table of statistics of
operations on the given host. The table shows statistics for each version of (versions 2, 3 and 4), giving the number of
times each procedure was requested and successfully serviced, the number and type of remote call requests that were made,
and information about RPC address lookups that were handled. This is useful for monitoring RPC activities on host.
Use portnum as the port number for the and options instead of the port number given by Use of this option avoids a call to the
remote to find out the address of the service. This option is made obsolete by the option.
Probe on host using version 2 of the protocol, and display a list of all registered RPC programs. If host is not specified, it
defaults to the local host. Note that version 2 of the protocol was previously known as the portmapper protocol.
Display a concise list of all registered RPC programs on
host. If host is not specified, it defaults to the local host.
Make an RPC call to procedure 0 of
prognum on the specified host using TCP, and report whether a response was received. This option is made obsolete by the
option as shown in the third synopsis.
Make an RPC call to procedure 0 of prognum on the specified host using UDP, and report whether a response was received. This option
is made obsolete by the option as shown in the third synopsis.
EXAMPLES
To show all of the RPC services registered on the local machine use:
To show all of the RPC services registered with on the machine named use:
To show whether the RPC service with program number prognum and version versnum is registered on the machine named for the transport TCP
use:
To show all RPC services registered with version 2 of the protocol on the local machine use:
To delete the registration for version 1 of the (program number service for all transports use:
or
AUTHOR
was developed by Sun Microsystems, Inc.
SEE ALSO rpcbind(1M), rpc(3N), netconfig(4), rpc(4).
rpcinfo(1M)