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 $
11 .Nd report RPC information
53 utility makes an RPC call to an RPC
54 server and reports what it finds.
56 In the first synopsis,
58 lists all the registered RPC services with
64 is not specified, the local host is the default.
67 is used, the information is displayed in a concise format.
69 In the second synopsis,
71 lists all the RPC services registered with
74 Also note that the format of the information
75 is different in the first and the second synopsis.
76 This is because the second synopsis is an older protocol used to
77 collect the information displayed (version 2 of the
81 The third synopsis makes an RPC call to procedure 0
88 and reports whether a response was received.
90 is the transport which has to be used for contacting the
92 The remote address of the service is obtained by
93 making a call to the remote
98 argument is a number that represents an RPC program number
103 attempts to call that version of the specified
107 attempts to find all the registered version
108 numbers for the specified
110 by calling version 0,
111 which is presumed not to exist;
114 attempts to obtain this information by calling
115 an extremely high version number instead,
116 and attempts to call each registered version.
118 the version number is required for
124 .Bl -tag -width indent
125 .It Fl T Ar transport
126 Specify the transport on which the service is required.
127 If this option is not specified,
129 uses the transport specified in the
131 environment variable, or if that is unset or empty, the transport
135 This is a generic option,
136 and can be used in conjunction with other options as
139 .It Fl a Ar serv_address
142 as the (universal) address for the service on
147 and report whether a response was received.
150 option is required with the
159 available version numbers for that program number.
160 This option avoids calls to remote
162 to find the address of the service.
165 is specified in universal address format of the given transport.
167 Make an RPC broadcast to procedure 0
172 and report all hosts that respond.
175 is specified, it broadcasts its request only on the
177 If broadcasting is not supported by any
179 an error message is printed.
180 Use of broadcasting should be limited because of the potential for adverse
181 effect on other systems.
183 Delete registration for the RPC service of the specified
190 unregister the service on only that transport,
191 otherwise unregister the service on all
192 the transports on which it was registered.
193 Only the owner of a service can delete a registration, except the
194 super-user who can delete any service.
196 Display a list of entries with a given
202 Entries are returned for all transports
203 in the same protocol family as that used to contact the remote
206 Display a table of statistics of
208 operations on the given
210 The table shows statistics for each version of
212 (versions 2, 3 and 4), giving the number of times each procedure was
213 requested and successfully serviced, the number and type of remote call
214 requests that were made, and information about RPC address lookups that were
216 This is useful for monitoring RPC activities on
221 as the port number for the
225 options instead of the port number given by
227 Use of this option avoids a call to the remote
229 to find out the address of the service.
239 using version 2 of the
242 and display a list of all registered RPC programs.
245 is not specified, it defaults to the local host.
246 Note: Version 2 of the
248 protocol was previously known as the portmapper protocol.
250 Display a concise list of all registered RPC programs on
254 is not specified, it defaults to the local host.
256 Make an RPC call to procedure 0 of
261 and report whether a response was received.
265 option as shown in the third synopsis.
267 Make an RPC call to procedure 0 of
272 and report whether a response was received.
276 option as shown in the third synopsis.
279 To show all of the RPC services registered on the local machine use:
281 .Dl "example% rpcinfo"
283 To show all of the RPC
284 services registered with
290 .Dl "example% rpcinfo klaxon"
292 The information displayed by the above commands can be quite lengthy.
295 option to display a more concise list:
297 .Dl "example$ rpcinfo -s klaxon"
298 .Bl -column "program" "version(s)" "unix,tcp,udp,tcp6,udp6" "nlockmgr" "super-user"
299 .It "program version(s) netid(s) service owner"
300 .It "100000 2,3,4 unix,tcp,udp,tcp6,udp6 rpcbind super-user"
301 .It "100008 1 udp,tcp,udp6,tcp6 walld super-user"
302 .It "100002 2,1 udp,udp6 rusersd super-user"
303 .It "100001 2,3,4 udp,udp6 rstatd super-user"
304 .It "100012 1 udp,tcp sprayd super-user"
305 .It "100007 3 udp,tcp ypbind super-user"
308 To show whether the RPC
309 service with program number
314 registered on the machine named
316 for the transport TCP
319 .Dl "example% rpcinfo -T tcp klaxon prognum versnum"
322 services registered with version 2 of the
324 protocol on the local machine use:
326 .Dl "example% rpcinfo -p"
328 To delete the registration for version
331 (program number 100008)
332 service for all transports use:
334 .Dl "example# rpcinfo -d 100008 1"
336 .Dl "example# rpcinfo -d walld 1"