RPCINFO(8) | System Manager's Manual | RPCINFO(8) |
rpcinfo |
[-m | -s] [host] |
rpcinfo | -p [host] |
rpcinfo | -T transport host prognum [versnum] |
rpcinfo | -l [-T transport] host prognum [versnum] |
rpcinfo | [-n portnum] -u host prognum [versnum] |
rpcinfo | [-n portnum] [-t] host prognum [versnum] |
rpcinfo | -a serv_address -T transport prognum [versnum] |
rpcinfo | -b [-T transport] prognum versnum |
rpcinfo | -d [-T transport] prognum versnum |
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. 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 rpcbind protocol).
The third synopsis makes an RPC call to procedure 0 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 rpcbind.
The prognum argument is a number that represents an RPC program number. If a versnum is specified, rpcinfo attempts to call that version of the specified prognum. Otherwise, rpcinfo 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, rpcinfo attempts to obtain this information by calling an extremely high version number instead, and attempts to call each registered version. Note: the version number is required for -b and -d options.
If versnum 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 serv_address is specified in universal address format of the given transport.
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,4 | local,tcp,udp,tcp6,udp6 | rpcbind | super-user |
100008 | 1 | udp,tcp,udp6,tcp6 | walld | super-user |
100002 | 2,1 | udp,udp6 | rusersd | super-user |
100001 | 2,3,4 | udp,udp6 | rstatd | super-user |
100012 | 1 | udp,tcp | sprayd | super-user |
100007 | 3 | udp,tcp | ypbind | super-user |
To show whether the RPC service with program number prognum and version versnum is registered on the machine named klaxon for the transport TCP use:
example% rpcinfo -T tcp klaxon prognum versnum
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
August 18, 1992 | NetBSD 6.1 |