rpcinfo

report RPC information

TLDR

Show full table of all RPC services registered on localhost

>_ rpcinfo
copy

Show concise table of all RPC services registered on localhost

>_ rpcinfo -s [localhost]
copy

Display table of statistics of rpcbind operations on localhost

>_ rpcinfo -m
copy

Display list of entries of given service name (mountd) and version number (2) on a remote nfs share

>_ rpcinfo -l [remote_nfs_server_ip] [mountd] [2]
copy

Delete the registration for version 1 of the mountd service for all transports

>_ rpcinfo -d [mountd] [1]
copy

SYNOPSIS

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

DESCRIPTION

rpcinfo 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. 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.

OPTIONS

EXAMPLES

To show all of the RPC services registered on the local machine use:

-literal example% rpcinfo

To show all of the RPC services registered with rpcbind on the machine named klaxon use:

-literal example% rpcinfo klaxon

The information displayed by the above commands can be quite lengthy. Use the -s option to display a more concise list:

-literal example$ rpcinfo -s klaxon

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:

-literal 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: -literal example% rpcinfo -p

To delete the registration for version 1 of the walld (program number 100008 ) service for all transports use: -literal example# rpcinfo -d 100008 1

or -literal example# rpcinfo -d walld 1

SEE ALSO

rpc(3), netconfig(5), rpc(5), rpcbind(8)

Copied to clipboard
free 100$ digital ocean credit