RPCBIND(8) NetBSD System Manager's Manual RPCBIND(8)
NAME
rpcbind - universal addresses to RPC program number mapper
SYNOPSIS
rpcbind [-dilLs]
DESCRIPTION
rpcbind is a server that converts RPC program numbers into universal ad- dresses. 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 should be started before any other RPC service. Normally, stan- dard 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 transla- tion-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. rpcbind can only be started by the super-user.
OPTIONS
-d Run in debug mode. In this mode, rpcbind will not fork when it starts, will print additional information during operation, and will abort on certain errors. With this option, the name-to-ad- dress translation consistency checks are shown in detail. -i ``insecure'' mode. Allows 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 li- brary and do not make those requests using the loopback inter- face. -l Turns on libwrap connection logging. -s causes rpcbind to change to the user daemon as soon as possible. This causes rpcbind to use non-privileged ports for outgoing con- nections, preventing non-privileged clients from using rpcbind to connect to services from a privileged port. -L Allow old-style local connections over the loopback interface. Without this flag, local connections are only allowed over a lo- cal socket, /var/run/rpcbind.sock
NOTES
All RPC servers must be restarted if rpcbind is restarted.
SEE ALSO
rpcinfo(1), rpcbind(3)
FILES
/var/run/rpcbind.sock Sep 14, 1992 1
Powered by man-cgi (2024-08-26). Maintained for NetBSD by Kimmo Suominen. Based on man-cgi by Panagiotis Christias.