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.
The 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.
When 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, rpcbind reports the condition and terminates.
The rpcbind utility can only be started by the super-user.
|Bind to AF_INET6 (IPv6) addresses only.
Run in debug mode.
In this mode,
will not fork when it starts, will print additional information
during operation, and will abort on certain errors if
IP addresses to bind to when servicing TCP and UDP requests.
may be specified multiple times and is typically necessary when running
on a multi-homed host.
|"Insecure" mode. Allow calls to SET and UNSET from any host. Normally rpcbind accepts 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.
|Allow old-style local connections over the loopback interface. Without this flag, local connections are only allowed over a local socket, /var/run/rpcbind.sock.
|Turn on libwrap connection logging.
|Cause rpcbind to change to the user daemon as soon as possible. This causes rpcbind to use non-privileged ports for outgoing connections, preventing non-privileged clients from using rpcbind to connect to services from a privileged port.
|Enable libwrap (TCP wrappers) support.
Enable the warmstart feature.
The warmstart feature saves RPC registrations on termination.
Any saved RPC registrations are restored on restart if
|saved portmap registrations file.
|saved rpcbind registrations file.
|socket used for local connections.
|April 19, 2017
|If you have a problem and you think awk(1) is the solution, then you have two problems.
|— David Tilbrook