rpcinfo
时间：2008-04-09 来源：nlchjian
NAME
rpcinfo - report RPC information
SYNOPSIS
[-m | -s] [host]
-p [host]
-T transport host prognum [versnum]
-l [-T transport] host prognum [versnum]
[-n portnum] -u host prognum [versnum]
[-n portnum] [-t] host prognum [versnum]
-a serv_address -T transport prognum [versnum]
-b [-T transport] prognum versnum
-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, ver-
sion 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 speci-
fied 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.
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,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 regis-
tered 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
rpcinfo - report RPC information
SYNOPSIS
[-m | -s] [host]
-p [host]
-T transport host prognum [versnum]
-l [-T transport] host prognum [versnum]
[-n portnum] -u host prognum [versnum]
[-n portnum] [-t] host prognum [versnum]
-a serv_address -T transport prognum [versnum]
-b [-T transport] prognum versnum
-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, ver-
sion 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 speci-
fied 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.
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,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 regis-
tered 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
相关阅读 更多 +
