1 .\" @(#)rpcinfo.1m 1.23 93/03/29 SMI; from SVr4
2 .\" Copyright 1989 AT&T
3 .\" Copyright 1991 Sun Microsystems, Inc.
4 .\" $NetBSD: rpcinfo.8,v 1.6 2000/06/02 23:19:38 fvdl Exp $
10 .Nd report RPC information
52 utility makes an RPC call to an RPC
53 server and reports what it finds.
55 In the first synopsis,
57 lists all the registered RPC services with
63 is not specified, the local host is the default.
66 is used, the information is displayed in a concise format.
68 In the second synopsis,
70 lists all the RPC services registered with
73 Also note that the format of the information
74 is different in the first and the second synopsis.
75 This is because the second synopsis is an older protocol used to
76 collect the information displayed (version 2 of the
80 The third synopsis makes an RPC call to procedure 0
87 and reports whether a response was received.
89 is the transport which has to be used for contacting the
91 The remote address of the service is obtained by
92 making a call to the remote
97 argument is a number that represents an RPC program number
102 attempts to call that version of the specified
106 attempts to find all the registered version
107 numbers for the specified
109 by calling version 0,
110 which is presumed not to exist;
113 attempts to obtain this information by calling
114 an extremely high version number instead,
115 and attempts to call each registered version.
117 the version number is required for
123 .Bl -tag -width indent
124 .It Fl T Ar transport
125 Specify the transport on which the service is required.
126 If this option is not specified,
128 uses the transport specified in the
130 environment variable, or if that is unset or empty, the transport
134 This is a generic option,
135 and can be used in conjunction with other options as
138 .It Fl a Ar serv_address
141 as the (universal) address for the service on
146 and report whether a response was received.
149 option is required with the
158 available version numbers for that program number.
159 This option avoids calls to remote
161 to find the address of the service.
164 is specified in universal address format of the given transport.
166 Make an RPC broadcast to procedure 0
171 and report all hosts that respond.
174 is specified, it broadcasts its request only on the
176 If broadcasting is not supported by any
178 an error message is printed.
179 Use of broadcasting should be limited because of the potential for adverse
180 effect on other systems.
182 Delete registration for the RPC service of the specified
189 unregister the service on only that transport,
190 otherwise unregister the service on all
191 the transports on which it was registered.
192 Only the owner of a service can delete a registration, except the
193 super-user who can delete any service.
195 Display a list of entries with a given
201 Entries are returned for all transports
202 in the same protocol family as that used to contact the remote
205 Display a table of statistics of
207 operations on the given
209 The table shows statistics for each version of
211 (versions 2, 3 and 4), giving the number of times each procedure was
212 requested and successfully serviced, the number and type of remote call
213 requests that were made, and information about RPC address lookups that were
215 This is useful for monitoring RPC activities on
220 as the port number for the
224 options instead of the port number given by
226 Use of this option avoids a call to the remote
228 to find out the address of the service.
238 using version 2 of the
241 and display a list of all registered RPC programs.
244 is not specified, it defaults to the local host.
245 Note: Version 2 of the
247 protocol was previously known as the portmapper protocol.
249 Display a concise list of all registered RPC programs on
253 is not specified, it defaults to the local host.
255 Make an RPC call to procedure 0 of
260 and report whether a response was received.
264 option as shown in the third synopsis.
266 Make an RPC call to procedure 0 of
271 and report whether a response was received.
275 option as shown in the third synopsis.
278 To show all of the RPC services registered on the local machine use:
280 .Dl "example% rpcinfo"
282 To show all of the RPC
283 services registered with
289 .Dl "example% rpcinfo klaxon"
291 The information displayed by the above commands can be quite lengthy.
294 option to display a more concise list:
296 .Dl "example$ rpcinfo -s klaxon"
297 .Bl -column "program" "version(s)" "unix,tcp,udp,tcp6,udp6" "nlockmgr" "super-user"
298 .It "program version(s) netid(s) service owner"
299 .It "100000 2,3,4 unix,tcp,udp,tcp6,udp6 rpcbind super-user"
300 .It "100008 1 udp,tcp,udp6,tcp6 walld super-user"
301 .It "100002 2,1 udp,udp6 rusersd super-user"
302 .It "100001 2,3,4 udp,udp6 rstatd super-user"
303 .It "100012 1 udp,tcp sprayd super-user"
304 .It "100007 3 udp,tcp ypbind super-user"
307 To show whether the RPC
308 service with program number
313 registered on the machine named
315 for the transport TCP
318 .Dl "example% rpcinfo -T tcp klaxon prognum versnum"
321 services registered with version 2 of the
323 protocol on the local machine use:
325 .Dl "example% rpcinfo -p"
327 To delete the registration for version
330 (program number 100008)
331 service for all transports use:
333 .Dl "example# rpcinfo -d 100008 1"
335 .Dl "example# rpcinfo -d walld 1"