|System Manager's Manual
universal addresses to RPC program number mapper
rpcbind utility is a server that
converts RPC program numbers into universal addresses. It must be running on
the host to be able to make RPC calls on a server on that machine.
When an RPC service is started, it tells
rpcbind the address at which it is listening, and
the RPC program numbers it is prepared to serve. When a client wishes to
make an RPC call to a given program number, it first contacts
rpcbind on the server machine to determine the
address where RPC requests should be sent.
rpcbind utility should be started
before any other RPC service. Normally, standard RPC servers are started by
port monitors, so
rpcbind must be started before
port monitors are invoked.
rpcbind is started, it checks that
certain name-to-address translation-calls function correctly. If they fail,
the network configuration databases may be corrupt. Since RPC services
cannot function correctly in this situation,
reports the condition and terminates.
rpcbind utility can only be started by
- When debugging (
-d), do an abort on errors.
- Run in debug mode. In this mode,
rpcbindwill log additional information during operation, and will abort on certain errors if
-ais also specified. With this option, the name-to-address translation consistency checks are shown in detail.
- Do not fork and become a background process.
- Specify specific IP addresses to bind to for UDP requests. This option may
be specified multiple times and can be used to restrict the interfaces
rpcbind will respond to. When specifying IP addresses with
rpcbindwill automatically add
127.0.0.1and if IPv6 is enabled,
::1to the list. If no
-hoption is specified,
rpcbindwill bind to
INADDR_ANY, which could lead to problems on a multi-homed host due to
rpcbindreturning a UDP packet from a different IP address than it was sent to. Note that when
rpcbindis controlled via systemd's socket activation, the
-hoption is ignored. In this case, you need to edit the
- “Insecure” mode. Allow calls to SET and UNSET from any host.
rpcbindaccepts these requests only from the loopback interface for security reasons. This change is necessary for programs that were compiled with earlier versions of the rpc library and do not make those requests using the loopback interface.
- Turn on libwrap connection logging.
rpcbindto change to the user daemon as soon as possible. This causes
rpcbindto use non-privileged ports for outgoing connections, preventing non-privileged clients from using
rpcbindto connect to services from a privileged port.
rpcbindto do a "warm start" by read a state file when
rpcbindstarts up. The state file is created when
All RPC servers must be restarted if
rpcbind is restarted.
|September 14, 1992