1 .\" Copyright 1989 AT&T
2 .\" Copyright 1991 Sun Microsystems, Inc.
3 .\" $NetBSD: rpcinfo.8,v 1.6 2000/06/02 23:19:38 fvdl Exp $
9 .Nd report RPC information
51 utility makes an RPC call to an RPC
52 server and reports what it finds.
54 In the first synopsis,
56 lists all the registered RPC services with
62 is not specified, the local host is the default.
65 is used, the information is displayed in a concise format.
67 In the second synopsis,
69 lists all the RPC services registered with
72 Also note that the format of the information
73 is different in the first and the second synopsis.
74 This is because the second synopsis is an older protocol used to
75 collect the information displayed (version 2 of the
79 The third synopsis makes an RPC call to procedure 0
86 and reports whether a response was received.
88 is the transport which has to be used for contacting the
90 The remote address of the service is obtained by
91 making a call to the remote
96 argument is a number that represents an RPC program number
101 attempts to call that version of the specified
105 attempts to find all the registered version
106 numbers for the specified
108 by calling version 0,
109 which is presumed not to exist;
112 attempts to obtain this information by calling
113 an extremely high version number instead,
114 and attempts to call each registered version.
116 the version number is required for
122 .Bl -tag -width indent
123 .It Fl T Ar transport
124 Specify the transport on which the service is required.
125 If this option is not specified,
127 uses the transport specified in the
129 environment variable, or if that is unset or empty, the transport
133 This is a generic option,
134 and can be used in conjunction with other options as
137 .It Fl a Ar serv_address
140 as the (universal) address for the service on
145 and report whether a response was received.
148 option is required with the
157 available version numbers for that program number.
158 This option avoids calls to remote
160 to find the address of the service.
163 is specified in universal address format of the given transport.
165 Make an RPC broadcast to procedure 0
170 and report all hosts that respond.
173 is specified, it broadcasts its request only on the
175 If broadcasting is not supported by any
177 an error message is printed.
178 Use of broadcasting should be limited because of the potential for adverse
179 effect on other systems.
181 Delete registration for the RPC service of the specified
188 unregister the service on only that transport,
189 otherwise unregister the service on all
190 the transports on which it was registered.
191 Only the owner of a service can delete a registration, except the
192 super-user who can delete any service.
194 Display a list of entries with a given
200 Entries are returned for all transports
201 in the same protocol family as that used to contact the remote
204 Display a table of statistics of
206 operations on the given
208 The table shows statistics for each version of
210 (versions 2, 3 and 4), giving the number of times each procedure was
211 requested and successfully serviced, the number and type of remote call
212 requests that were made, and information about RPC address lookups that were
214 This is useful for monitoring RPC activities on
219 as the port number for the
223 options instead of the port number given by
225 Use of this option avoids a call to the remote
227 to find out the address of the service.
237 using version 2 of the
240 and display a list of all registered RPC programs.
243 is not specified, it defaults to the local host.
244 Note: Version 2 of the
246 protocol was previously known as the portmapper protocol.
248 Display a concise list of all registered RPC programs on
252 is not specified, it defaults to the local host.
254 Make an RPC call to procedure 0 of
259 and report whether a response was received.
263 option as shown in the third synopsis.
265 Make an RPC call to procedure 0 of
270 and report whether a response was received.
274 option as shown in the third synopsis.
277 To show all of the RPC services registered on the local machine use:
279 .Dl "example% rpcinfo"
281 To show all of the RPC
282 services registered with
288 .Dl "example% rpcinfo klaxon"
290 The information displayed by the above commands can be quite lengthy.
293 option to display a more concise list:
295 .Dl "example$ rpcinfo -s klaxon"
296 .Bl -column "program" "version(s)" "unix,tcp,udp,tcp6,udp6" "nlockmgr" "super-user"
297 .It "program version(s) netid(s) service owner"
298 .It "100000 2,3,4 unix,tcp,udp,tcp6,udp6 rpcbind super-user"
299 .It "100008 1 udp,tcp,udp6,tcp6 walld super-user"
300 .It "100002 2,1 udp,udp6 rusersd super-user"
301 .It "100001 2,3,4 udp,udp6 rstatd super-user"
302 .It "100012 1 udp,tcp sprayd super-user"
303 .It "100007 3 udp,tcp ypbind super-user"
306 To show whether the RPC
307 service with program number
312 registered on the machine named
314 for the transport TCP
317 .Dl "example% rpcinfo -T tcp klaxon prognum versnum"
320 services registered with version 2 of the
322 protocol on the local machine use:
324 .Dl "example% rpcinfo -p"
326 To delete the registration for version
329 (program number 100008)
330 service for all transports use:
332 .Dl "example# rpcinfo -d 100008 1"
334 .Dl "example# rpcinfo -d walld 1"