1
2RPCBIND(8)                BSD System Manager's Manual               RPCBIND(8)
3

NAME

5     rpcbind — universal addresses to RPC program number mapper
6

SYNOPSIS

8     rpcbind [-adhiLls]
9

DESCRIPTION

11     The rpcbind utility is a server that converts RPC program numbers into
12     universal addresses.  It must be running on the host to be able to make
13     RPC calls on a server on that machine.
14
15     When an RPC service is started, it tells rpcbind the address at which it
16     is listening, and the RPC program numbers it is prepared to serve.  When
17     a client wishes to make an RPC call to a given program number, it first
18     contacts rpcbind on the server machine to determine the address where RPC
19     requests should be sent.
20
21     The rpcbind utility should be started before any other RPC service.  Nor‐
22     mally, standard RPC servers are started by port monitors, so rpcbind must
23     be started before port monitors are invoked.
24
25     When rpcbind is started, it checks that certain name-to-address transla‐
26     tion-calls function correctly.  If they fail, the network configuration
27     databases may be corrupt.  Since RPC services cannot function correctly
28     in this situation, rpcbind reports the condition and terminates.
29
30     The rpcbind utility can only be started by the super-user.
31

OPTIONS

33     -a      When debugging (-d), do an abort on errors.
34
35     -d      Run in debug mode.  In this mode, rpcbind will not fork when it
36             starts, will print additional information during operation, and
37             will abort on certain errors if -a is also specified.  With this
38             option, the name-to-address translation consistency checks are
39             shown in detail.
40
41     -h      Specify specific IP addresses to bind to for UDP requests.  This
42             option may be specified multiple times and is typically necessary
43             when running on a multi-homed host.  If no -h option is speci‐
44             fied, rpcbind will bind to INADDR_ANY, which could lead to prob‐
45             lems on a multi-homed host due to rpcbind returning a UDP packet
46             from a different IP address than it was sent to.  Note that when
47             specifying IP addresses with -h, rpcbind will automatically add
48             127.0.0.1 and if IPv6 is enabled, ::1 to the list.
49
50     -i      “Insecure” mode.  Allow calls to SET and UNSET from any host.
51             Normally rpcbind accepts these requests only from the loopback
52             interface for security reasons.  This change is necessary for
53             programs that were compiled with earlier versions of the rpc
54             library and do not make those requests using the loopback inter‐
55             face.
56
57     -L      Allow old-style local connections over the loopback interface.
58             Without this flag, local connections are only allowed over a
59             local socket, /var/run/rpcbind.sock.
60
61     -l      Turn on libwrap connection logging.
62
63     -s      Cause rpcbind to change to the user daemon as soon as possible.
64             This causes rpcbind to use non-privileged ports for outgoing con‐
65             nections, preventing non-privileged clients from using rpcbind to
66             connect to services from a privileged port.
67
68     -w      Cause rpcbind to do a "warm start" by read a state file when
69             rpcbind starts up. The state file is created when rpcbind termi‐
70             nates.
71

NOTES

73     All RPC servers must be restarted if rpcbind is restarted.
74

SEE ALSO

76     rpcbind(3), rpcinfo(8)
77

LINUX PORT

79BSD                           September 14, 1992                           BSD