|RPCBIND(8)||Maintenance Commands and Procedures||RPCBIND(8)|
rpcbind [-d] [-w] [-l listen_backlog]
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 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 can be corrupt. Since RPC services cannot function correctly in this situation, rpcbind reports the condition and terminates.
rpcbind maintains an open transport end for each transport that it uses for indirect calls. This is the UDP port on most systems.
The rpcbind service is managed by the service management facility, smf(7), under the service identifier:
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(8). rpcbind can only be started by the superuser or someone in the Primary Administrator role.
The configuration properties of this service can be modified with svccfg(8).
The following SMF property is used to allow or disallow access to rpcbind by remote clients:
config/local_only = true
The default value, true, shown above, disallows remote access; a value of false allows remove access. See EXAMPLES.
The FMRI svc:network/rpc/bind property group config contains the following property settings:
The following sequence of commands allows remote access to rpcbind.
# svccfg -s svc:/network/rpc/bind setprop config/local_only = false # svcadm refresh svc:/network/rpc/bind
|ATTRIBUTE TYPE||ATTRIBUTE VALUE|
|Interface Stability||See below.|
TCP wrappers is External.
All RPC servers are restarted if the following occurs: rpcbind crashes (or is killed with SIGKILL) and is unable to write the warm-start files; rpcbind is started without the -w option after a graceful termination. Otherwise, the warm start files are not found by rpcbind.
|May 13, 2017||OmniOS|