Map RPC program numbers into universal addresses
The rpcbind server converts RPC program numbers into universal addresses. You must run this utility on the host to make RPC calls on a server.
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 is secure by default, and can be started only by the superuser.|
Standard RPC servers can be run by inetd, so you must start rpcbind before inetd is invoked.
|The tiny TCP/IP stack (npm-ttcpip.so) doesn't support rpcbind utility -- when the utility is run in secure mode, and uses Unix domain sockets. Use both -L and -i rpcbind options together, if you want to use this utility in combination with the tiny TCP/IP stack.|
The rpcbind utility needs /etc/netconfig, as well as the following entries in /etc/services:
sunrpc 111/tcp rpcbind portmap sunrpc 111/udp rpcbind portmap
It also requires the librpc shared library.
If you restart rpcbind, you must restart all RPC servers.