1RPCINFO(8) BSD System Manager's Manual RPCINFO(8)
2
4 rpcinfo — report RPC information
5
7 rpcinfo [-m | -s] [host]
8 rpcinfo -p [host]
9 rpcinfo -T transport host prognum [versnum]
10 rpcinfo -l [-T transport] host prognum [versnum]
11 rpcinfo [-n portnum] -u host prognum [versnum]
12 rpcinfo [-n portnum] [-t] host prognum [versnum]
13 rpcinfo -a serv_address -T transport prognum [versnum]
14 rpcinfo -b [-T transport] prognum versnum
15 rpcinfo -d [-T transport] prognum versnum
16
18 rpcinfo makes an RPC call to an RPC server and reports what it finds.
19 In the first synopsis, rpcinfo lists all the registered RPC services with
21 rpcbind on host. If host is not specified, the local host is the
22 default. If -s is used, the information is displayed in a concise for‐
23 mat.
24 In the second synopsis, rpcinfo lists all the RPC services registered
26 with rpcbind, version 2. Also note that the format of the information is
27 different in the first and the second synopsis. This is because the sec‐
28 ond synopsis is an older protocol used to collect the information dis‐
29 played (version 2 of the rpcbind protocol).
30 The third synopsis makes an RPC call to procedure 0 of prognum and
32 versnum on the specified host and reports whether a response was
33 received. transport is the transport which has to be used for contacting
34 the given service. The remote address of the service is obtained by mak‐
35 ing a call to the remote rpcbind.
36 The prognum argument is a number that represents an RPC program number.
38 If a versnum is specified, rpcinfo attempts to call that version of the
39 specified prognum. Otherwise, rpcinfo attempts to find all the regis‐
40 tered version numbers for the specified prognum by calling version 0,
41 which is presumed not to exist; if it does exist, rpcinfo attempts to
42 obtain this information by calling an extremely high version number
43 instead, and attempts to call each registered version. Note: the version
44 number is required for -b and -d options.
45
47 -T transport
48 Specify the transport on which the service is required. If this
49 option is not specified, rpcinfo uses the transport specified in
50 the NETPATH environment variable, or if that is unset or null,
51 the transport in the netconfig(5) database is used. This is a
52 generic option, and can be used in conjunction with other options
53 as shown in the SYNOPSIS.
54 -a serv_address
56 Use serv_address as the (universal) address for the service on
57 transport to ping procedure 0 of the specified prognum and report
58 whether a response was received. The -T option is required with
59 the -a option.
60 If versnum is not specified, rpcinfo tries to ping all available
62 version numbers for that program number. This option avoids
63 calls to remote rpcbind to find the address of the service. The
64 serv_address is specified in universal address format of the
65 given transport.
66 -b Make an RPC broadcast to procedure 0 of the specified prognum and
68 versnum and report all hosts that respond. If transport is spec‐
69 ified, it broadcasts its request only on the specified transport.
70 If broadcasting is not supported by any transport, an error mes‐
71 sage is printed. Use of broadcasting should be limited because
72 of the potential for adverse effect on other systems.
73 -d Delete registration for the RPC service of the specified prognum
75 and versnum. If transport is specified, unregister the service
76 on only that transport, otherwise unregister the service on all
77 the transports on which it was registered. Only the owner of a
78 service can delete a registration, except the super-user who can
79 delete any service.
80 -l Display a list of entries with a given prognum and versnum on the
82 specified host. Entries are returned for all transports in the
83 same protocol family as that used to contact the remote rpcbind.
84 -m Display a table of statistics of rpcbind operations on the given
86 host. The table shows statistics for each version of rpcbind
87 (versions 2, 3 and 4), giving the number of times each procedure
88 was requested and successfully serviced, the number and type of
89 remote call requests that were made, and information about RPC
90 address lookups that were handled. This is useful for monitoring
91 RPC activities on host.
92 -n portnum
94 Use portnum as the port number for the -t and -u options instead
95 of the port number given by rpcbind. Use of this option avoids a
96 call to the remote rpcbind to find out the address of the ser‐
97 vice. This option is made obsolete by the -a option.
98 -p Probe rpcbind on host using version 2 of the rpcbind protocol,
100 and display a list of all registered RPC programs. If host is
101 not specified, it defaults to the local host. Note: Version 2 of
102 the rpcbind protocol was previously known as the portmapper pro‐
103 tocol.
104 -s Display a concise list of all registered RPC programs on host.
106 If host is not specified, it defaults to the local host.
107 -t Make an RPC call to procedure 0 of prognum on the specified host
109 using TCP, and report whether a response was received. This
110 option is made obsolete by the -T option as shown in the third
111 synopsis.
112 -u Make an RPC call to procedure 0 of prognum on the specified host
114 using UDP, and report whether a response was received. This
115 option is made obsolete by the -T option as shown in the third
116 synopsis.
117
119 To show all of the RPC services registered on the local machine use:
120 example% rpcinfo
122 To show all of the RPC services registered with rpcbind on the machine
124 named klaxon use:
125 example% rpcinfo klaxon
127 The information displayed by the above commands can be quite lengthy.
129 Use the -s option to display a more concise list:
130 example$ rpcinfo -s klaxon
132 program version(s) netid(s) service owner
134 100000 2,3,4 local,tcp,udp,tcp6,udp6 rpcbind super-user
135 100008 1 udp,tcp,udp6,tcp6 walld super-user
136 100002 2,1 udp,udp6 rusersd super-user
137 100001 2,3,4 udp,udp6 rstatd super-user
138 100012 1 udp,tcp sprayd super-user
139 100007 3 udp,tcp ypbind super-user
140 To show whether the RPC service with program number prognum and version
142 versnum is registered on the machine named klaxon for the transport TCP
143 use:
144 example% rpcinfo -T tcp klaxon prognum versnum
146 To show all RPC services registered with version 2 of the rpcbind proto‐
148 col on the local machine use:
149 example% rpcinfo -p
151 To delete the registration for version 1 of the walld (program number
153 100008 ) service for all transports use:
154 example# rpcinfo -d 100008 1
156 or
158 example# rpcinfo -d walld 1
160
162 rpc(3), netconfig(5), rpc(5), rpcbind(8)
163 August 18, 1992