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 log additional in‐
36             formation during operation, and will abort on certain errors if
37             -a is also specified.  With this option, the name-to-address
38             translation consistency checks are shown in detail.
39
40     -f      Do not fork and become a background process.
41
42     -h      Specify specific IP addresses to bind to for UDP requests.  This
43             option may be specified multiple times and can be used to re‐
44             strict the interfaces rpcbind will respond to.  When specifying
45             IP addresses with -h, rpcbind will automatically add 127.0.0.1
46             and if IPv6 is enabled, ::1 to the list.  If no -h option is
47             specified, rpcbind will bind to INADDR_ANY, which could lead to
48             problems on a multi-homed host due to rpcbind returning a UDP
49             packet from a different IP address than it was sent to.  Note
50             that when rpcbind is controlled via systemd's socket activation,
51             the -h option is ignored. In this case, you need to edit the
52             ListenStream and ListenDgram definitions in
53             /usr/lib/systemd/system/rpcbind.socket instead.
54
55     -i      “Insecure” mode.  Allow calls to SET and UNSET from any host.
56             Normally rpcbind accepts these requests only from the loopback
57             interface for security reasons.  This change is necessary for
58             programs that were compiled with earlier versions of the rpc li‐
59             brary and do not make those requests using the loopback inter‐
60             face.
61
62     -l      Turn on libwrap connection logging.
63
64     -s      Cause rpcbind to change to the user daemon as soon as possible.
65             This causes rpcbind to use non-privileged ports for outgoing con‐
66             nections, preventing non-privileged clients from using rpcbind to
67             connect to services from a privileged port.
68
69     -w      Cause rpcbind to do a "warm start" by read a state file when
70             rpcbind starts up. The state file is created when rpcbind termi‐
71             nates.
72

NOTES

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

SEE ALSO

77     rpcinfo(8)
78

LINUX PORT

80BSD                           September 14, 1992                           BSD