1rpcinfo(1M) System Administration Commands rpcinfo(1M)
2
6 rpcinfo - report RPC information
7
9 rpcinfo [-m | -s] [host]
10 rpcinfo -p [host]
13 rpcinfo -T transport host prognum [versnum]
16 rpcinfo -l [-T transport] host prognum versnum
19 rpcinfo [-n portnum] -u host prognum [versnum]
22 rpcinfo [-n portnum] -t host prognum [versnum]
25 rpcinfo -a serv_address -T transport prognum [versnum]
28 rpcinfo -b [-T transport] prognum versnum
31 rpcinfo -d [-T transport] prognum versnum
34
37 rpcinfo makes an RPC call to an RPC server and reports what it finds.
38 In the first synopsis, rpcinfo lists all the registered RPC services
41 with rpcbind on host. If host is not specified, the local host is the
42 default. If -s is used, the information is displayed in a concise for‐
43 mat.
44 In the second synopsis, rpcinfo lists all the RPC services registered
47 with rpcbind, version 2. Note that the format of the information is
48 different in the first and the second synopsis. This is because the
49 second synopsis is an older protocol used to collect the information
50 displayed (version 2 of the rpcbind protocol).
51 The third synopsis makes an RPC call to procedure 0 of prognum and ver‐
54 snum on the specified host and reports whether a response was received.
55 transport is the transport which has to be used for contacting the
56 given service. The remote address of the service is obtained by making
57 a call to the remote rpcbind.
58 The prognum argument is a number that represents an RPC program number
61 (see rpc(4)).
62 If a versnum is specified, rpcinfo attempts to call that version of the
65 specified prognum. Otherwise, rpcinfo attempts to find all the regis‐
66 tered version numbers for the specified prognum by calling version 0,
67 which is presumed not to exist; if it does exist, rpcinfo attempts to
68 obtain this information by calling an extremely high version number
69 instead, and attempts to call each registered version. Note that the
70 version number is required for -b and -d options.
71 The EXAMPLES section describe other ways of using rpcinfo.
74
76 -T transport Specify the transport on which the service is
77 required. If this option is not specified, rpcinfo
78 uses the transport specified in the NETPATH environ‐
79 ment variable, or if that is unset or NULL, the
80 transport in the netconfig(4) database is used. This
81 is a generic option, and can be used in conjunction
82 with other options as shown in the SYNOPSIS.
83 -a serv_address Use serv_address as the (universal) address for the
86 service on transport to ping procedure 0 of the
87 specified prognum and report whether a response was
88 received. The -T option is required with the -a
89 option. If versnum is not specified, rpcinfo tries
90 to ping all available version numbers for that pro‐
91 gram number. This option avoids calls to remote
92 rpcbind to find the address of the service. The
93 serv_address is specified in universal address for‐
94 mat of the given transport.
95 -b Make an RPC broadcast to procedure 0 of the speci‐
98 fied prognum and versnum and report all hosts that
99 respond. If transport is specified, it broadcasts
100 its request only on the specified transport. If
101 broadcasting is not supported by any transport, an
102 error message is printed. Use of broadcasting should
103 be limited because of the potential for adverse
104 effect on other systems.
105 -d Delete registration for the RPC service of the spec‐
108 ified prognum and versnum. If transport is speci‐
109 fied, unregister the service on only that transport,
110 otherwise unregister the service on all the trans‐
111 ports on which it was registered. Only the owner of
112 a service can delete a registration, except the
113 superuser, who can delete any service.
114 -l Display a list of entries with a given prognum and
117 versnum on the specified host. Entries are returned
118 for all transports in the same protocol family as
119 that used to contact the remote rpcbind.
120 -m Display a table of statistics of rpcbind operations
123 on the given host. The table shows statistics for
124 each version of rpcbind (versions 2, 3 and 4), giv‐
125 ing the number of times each procedure was requested
126 and successfully serviced, the number and type of
127 remote call requests that were made, and information
128 about RPC address lookups that were handled. This is
129 useful for monitoring RPC activities on host.
130 -n portnum Use portnum as the port number for the -t and -u
133 options instead of the port number given by rpcbind.
134 Use of this option avoids a call to the remote
135 rpcbind to find out the address of the service. This
136 option is made obsolete by the -a option.
137 -p Probe rpcbind on host using version 2 of the rpcbind
140 protocol, and display a list of all registered RPC
141 programs. If host is not specified, it defaults to
142 the local host. This option is not useful for IPv6;
143 use -s (see below) instead. Note that version 2 of
144 the rpcbind protocol was previously known as the
145 portmapper protocol.
146 -s Display a concise list of all registered RPC pro‐
149 grams on host. If host is not specified, it defaults
150 to the local host.
151 -t Make an RPC call to procedure 0 of prognum on the
154 specified host using TCP, and report whether a
155 response was received. This option is made obsolete
156 by the -T option as shown in the third synopsis.
157 -u Make an RPC call to procedure 0 of prognum on the
160 specified host using UDP, and report whether a
161 response was received. This option is made obsolete
162 by the -T option as shown in the third synopsis.
163
166 Example 1 RPC services.
167 To show all of the RPC services registered on the local machine use:
170 example% rpcinfo
173 To show all of the RPC services registered with rpcbind on the machine
178 named klaxon use:
179 example% rpcinfo klaxon
182 The information displayed by the above commands can be quite lengthy.
187 Use the -s option to display a more concise list:
188 example% rpcinfo -s klaxon
191 program vrsn netid(s) service owner
198 100000 2,3,4 tcp,udp,ticlts,ticots,ticotsord rpcbind superuser
199 100008 1 ticotsord,ticots,ticlts,udp,tcp walld superuser
200 100002 2,1 ticotsord,ticots,ticlts,udp,tcp rusersd superuser
201 100001 2,3,4 ticotsord,ticots,tcp,ticlts,udp rstatd superuser
202 100012 1 ticotsord,ticots,ticlts,udp,tcp sprayd superuser
204 100007 3 ticotsord,ticots,ticlts,udp,tcp ypbind superuser
205 100029 1 ticotsord,ticots,ticlts keyserv superuser
206 100078 4 ticotsord,ticots,ticlts - superuser
207 100024 1 ticotsord,ticots,ticlts,udp,tcp status superuser
208 100021 2,1 ticotsord,ticots,ticlts,udp,tcp nlockmgr superuser
209 100020 1 ticotsord,ticots,ticlts,udp,tcp llockmgr superuser
210 To show whether the RPC service with program number prognum and version
214 versnum is registered on the machine named klaxon for the transport TCP
215 use:
216 example% rpcinfo -T tcp klaxon prognum versnum
219 To show all RPC services registered with version 2 of the rpcbind pro‐
224 tocol on the local machine use:
225 example% rpcinfo -p
228 To delete the registration for version 1 of the walld (program number
233 100008) service for all transports use:
234 example# rpcinfo -d 100008 1
237 or
242 example# rpcinfo -d walld 1
245
249 See attributes(5) for descriptions of the following attributes:
250 ┌─────────────────────────────┬─────────────────────────────┐
255 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
256 ├─────────────────────────────┼─────────────────────────────┤
257 │Availability │SUNWcsu │
258 └─────────────────────────────┴─────────────────────────────┘
259
261 rpcbind(1M), rpc(3NSL), netconfig(4), rpc(4), attributes(5)
262SunOS 5.11 13 Jul 2001 rpcinfo(1M)