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.13 2003/02/25 10:35:53 wiz Exp $
10 .Nd report RPC information
44 .Ar prognum Ar versnum
48 .Ar prognum Ar versnum
51 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 null, the transport
133 This is a generic option,
134 and can be used in conjunction with other options as
135 shown in the SYNOPSIS.
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.
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.
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.
197 Display a list of entries with a given
203 Entries are returned for all transports
204 in the same protocol family as that used to contact the remote
208 Display a table of statistics of
210 operations on the given
212 The table shows statistics for each version of
214 (versions 2, 3 and 4), giving the number of times each procedure was
215 requested and successfully serviced, the number and type of remote call
216 requests that were made, and information about RPC address lookups that were
217 handled. This is useful for monitoring RPC activities on
223 as the port number for the
227 options instead of the port number given by
229 Use of this option avoids a call to the remote
231 to find out the address of the service. This option is made
241 using version 2 of the
244 and display a list of all registered RPC programs.
247 is not specified, it defaults to the local host.
248 Note: Version 2 of the
250 protocol was previously known as the portmapper protocol.
253 Display a concise list of all registered RPC programs on
257 is not specified, it defaults to the local host.
260 Make an RPC call to procedure 0 of
265 and report whether a response was received. This option is made
268 option as shown in the third synopsis.
271 Make an RPC call to procedure 0 of
276 and report whether a response was received. This option is made
279 option as shown in the third synopsis.
282 To show all of the RPC services registered on the local machine use:
288 To show all of the RPC
289 services registered with
296 example% rpcinfo klaxon
299 The information displayed by the above commands can be quite lengthy.
302 option to display a more concise list:
305 example$ rpcinfo -s klaxon
307 .Bl -column "program" "version(s)" "local,tcp,udp,tcp6,udp6" "nlockmgr" "super-user"
308 .It program Ta version(s) Ta netid(s) Ta service Ta owner
309 .It 100000 Ta 2,3,4 Ta local,tcp,udp,tcp6,udp6 Ta rpcbind Ta super-user
310 .It 100008 Ta 1 Ta udp,tcp,udp6,tcp6 Ta walld Ta super-user
311 .It 100002 Ta 2,1 Ta udp,udp6 Ta rusersd Ta super-user
312 .It 100001 Ta 2,3,4 Ta udp,udp6 Ta rstatd Ta super-user
313 .It 100012 Ta 1 Ta udp,tcp Ta sprayd Ta super-user
314 .It 100007 Ta 3 Ta udp,tcp Ta ypbind Ta super-user
317 To show whether the RPC
318 service with program number
322 is registered on the machine named
324 for the transport TCP
328 example% rpcinfo -T tcp klaxon prognum versnum
332 services registered with version 2 of the
334 protocol on the local machine use:
339 To delete the registration for version
342 (program number 100008 )
343 service for all transports use:
345 example# rpcinfo -d 100008 1
350 example# rpcinfo -d walld 1