rpcinfo(1M)rpcinfo(1M)NAMErpcinfo - report RPC information
SYNOPSIS
/usr/etc/rpcinfo [ -s ] [ host ]
/usr/etc/rpcinfo -p [ host ]
/usr/etc/rpcinfo -T transport host program-number [ version-number ]
/usr/etc/rpcinfo -l [ -T transport ] host program-number version-number
/usr/etc/rpcinfo [ -n port | -C ] -u host program-number [ version-number ]
/usr/etc/rpcinfo [ -n port ] -t host program-number [ version-number ]
/usr/etc/rpcinfo -a uaddress -T transport program-number [ version-number ]
/usr/etc/rpcinfo -b [ -T transport ] program-number version-number
/usr/etc/rpcinfo -m [ -T transport ] program-number version-number
/usr/etc/rpcinfo -d [ -T transport ] program-number version-number
/usr/etc/rpcinfo -M [ host ]
DESCRIPTIONrpcinfo makes an RPC call to an RPC server and reports what it finds.
In the first synopsis, rpcinfo lists all the registered RPC services with
rpcbind on host. If host is not specified, the local host is the
default. If -s is used, the information is displayed in a concise format.
In the second synopsis, rpcinfo lists all the RPC services registered
with rpcbind, version 2 (previously called portmap). 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 rpcbind protocol).
The third synopsis makes an RPC call to procedure 0 of program-number and
version-number 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, e.g. udp or tcp. The remote address of the service is
obtained by making a call to the remote rpcbind.
The program-number argument is either a name or a number that represents
an RPC program number (see rpc(4)).
If a version-number is specified, rpcinfo attempts to call that version
of the specified program-number. Otherwise, rpcinfo attempts to find all
the registered version numbers for the specified program-number by
calling version 0, which is presumed not to exist; if it does exist,
rpcinfo attempts to obtain this information by calling an extremely high
version number instead, A call to a non-existent version will result in
an error response which includes the minimum and maximum registered
versions. Rpcinfo will attempt to call every version in this range.
Note that the version number is required for -b and -d options.
The EXAMPLES section describe other ways of using rpcinfo.
Page 1
rpcinfo(1M)rpcinfo(1M)OPTIONS-M Display a table of statistics of rpcbind operations on the given
host. The table shows statistics for each version of rpcbind
(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. (See the NOTES section below).
-T transport
Specify the transport on which the service is required. If this
option is not specified, rpcinfo uses the transport specified in the
NETPATH 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 SYNOPSIS.
-a uaddress
Use uaddress as the universal address for the service on transport
to ping procedure 0 of the specified program-number and report
whether a response was received. The -T option is required with the
-a option.
If version-number is not specified, rpcinfo tries to ping all
available version numbers for that program number. This option
avoids calls to remote rpcbind to find the address of the service.
The uaddress is specified in universal address format of the given
transport.
-b Make an RPC broadcast to procedure 0 of the specified program-number
and version-number 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.
-m Like -b but uses an RPC multicast (see the NOTES section below).
-d Delete registration for the RPC service of the specified program-
number and version-number. 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 superuser who can
delete any service.
-l Display a list of entries with a given program-number and version-
number on the specified host. Entries are returned for all
transports in the same protocol family as that used to contact the
remote rpcbind.
Page 2
rpcinfo(1M)rpcinfo(1M)-n port
Use port as the port number for the -t and -u options instead of the
port number given by rpcbind. Use of this option avoids a call to
the remote rpcbind to find out the address of the service. This
option is made obsolete by the -a option.
-p Probe rpcbind on host using version 2 of the rpcbind 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
rpcbind protocol was previously known as the portmapper protocol.
-s Display a concise list of all registered RPC programs on host. If
host is not specified, it defaults to the local host.
-t Make an RPC call to procedure 0 of program-number on the specified
host using TCP, and report whether a response was received. This
option is made obsolete by the -T option as shown in the third
synopsis.
-u Make an RPC call to procedure 0 of program-number on the specified
host using UDP, and report whether a response was received.
If -C is used in conjunction with -u and a version-number is
specified, a call to PMAPPROC_CALLIT will be made rather than
PMAPPROC_GETPORT followed by the call to procedure 0.
This option is made obsolete by the -T option as shown in the third
synopsis.
EXAMPLES
To show all of the RPC services registered on the local machine use:
example% rpcinfo
To show all of the RPC services registered with rpcbind on the machine
named klaxon use:
example% rpcinfo klaxon
The information displayed by the above commands can be quite lengthy. Use
the -s option to display a more concise list:
example% rpcinfo-s klaxon
program version(s)netid(s) service owner
100000 2,3 ticlts,ticots,ticotsord,tcp,udp portmapper superuser
100003 3,2 tcp,udp nfs superuser
100024 1 tcp,udp status superuser
100021 4,3,1 tcp,udp nlockmgr superuser
100099 1 udp autofsd superuser
Page 3
rpcinfo(1M)rpcinfo(1M)
100005 3,1 udp,tcp mountd superuser
391004 1 udp,tcp sgi_mountd superuser
100001 3,2,1 udp rstatd superuser
100008 1 udp walld superuser
100002 1 udp rusersd superuser
100011 1 udp rquotad superuser
100012 1 udp sprayd superuser
391011 1 tcp sgi_videod superuser
391002 2,1 tcp sgi_fam superuser
391006 1 udp sgi_pcsd superuser
391009 1 tcp sgi_pod superuser
391029 1 tcp sgi_espd superuser
100083 1 tcp ttdbserverd superuser
To show whether the RPC service with program number program-number and
version version-number is registered on the machine named klaxon for the
transport TCP use:
example% rpcinfo-T tcp klaxon program-number version-number
To show all RPC services registered with version 2 of the rpcbind
protocol on the local machine use:
example% rpcinfo-p
To delete the registration for version 1 of the walld (program number
100008) service for all transports use:
example# rpcinfo-d 100008 1
or
example# rpcinfo-d walld 1
NOTES
The -C, -m, and -M, options are specific to IRIX. Some other operating
systems use the -m option instead of -M for retrieving rpcbind statistics
and do not implement -C; strict commandline compatibility with these
operating systems can be achieved by using the option --sun-options as
the first argument to rpcbind.
Some of the options (-M, -l) require rpcbind protocol version 3 or
version 4 features, and will not work if the queried host runs older
versions of the rpcbind protocol (e.g. a Linux machine or an IRIX machine
running the /usr/etc/portmap server or some versions of
/usr/etc/rpcbind).
Page 4
rpcinfo(1M)rpcinfo(1M)FILES
/etc/rpc names for rpc program numbers
SEE ALSOportmap(1M), netconfig(4), rpc(4).
IRIX Network Programming Guide
Page 5
