1.\" @(#)rpcbind.1m 1.19 92/09/14 SMI; from SVr4 2.\" Copyright 1989 AT&T 3.\" Copyright 1991 Sun Microsystems, Inc. 4.\" $FreeBSD$ 5.Dd November 7, 2004 6.Dt RPCBIND 8 7.Os 8.Sh NAME 9.Nm rpcbind 10.Nd universal addresses to RPC program number mapper 11.Sh SYNOPSIS 12.Nm 13.Op Fl adiLls 14.Op Fl h Ar bindip 15.Sh DESCRIPTION 16The 17.Nm 18utility is a server that converts 19.Tn RPC 20program numbers into 21universal addresses. 22It must be running on the host to be able to make 23.Tn RPC 24calls 25on a server on that machine. 26.Pp 27When an 28.Tn RPC 29service is started, 30it tells 31.Nm 32the address at which it is listening, 33and the 34.Tn RPC 35program numbers it is prepared to serve. 36When a client wishes to make an 37.Tn RPC 38call to a given program number, 39it first contacts 40.Nm 41on the server machine to determine 42the address where 43.Tn RPC 44requests should be sent. 45.Pp 46The 47.Nm 48utility should be started before any other RPC service. 49Normally, standard 50.Tn RPC 51servers are started by port monitors, so 52.Nm 53must be started before port monitors are invoked. 54.Pp 55When 56.Nm 57is started, it checks that certain name-to-address 58translation-calls function correctly. 59If they fail, the network configuration databases may be corrupt. 60Since 61.Tn RPC 62services cannot function correctly in this situation, 63.Nm 64reports the condition and terminates. 65.Pp 66The 67.Nm 68utility can only be started by the super-user. 69.Sh OPTIONS 70.Bl -tag -width indent 71.It Fl a 72When debugging 73.Pq Fl d , 74do an abort on errors. 75.It Fl d 76Run in debug mode. 77In this mode, 78.Nm 79will not fork when it starts, will print additional information 80during operation, and will abort on certain errors if 81.Fl a 82is also specified. 83With this option, the name-to-address translation consistency 84checks are shown in detail. 85.It Fl h Ar bindip 86Specify specific IP addresses to bind to for UDP requests. 87This option 88may be specified multiple times and is typically necessary when running 89on a multi-homed host. 90If no 91.Fl h 92option is specified, 93.Nm 94will bind to 95.Dv INADDR_ANY , 96which could lead to problems on a multi-homed host due to 97.Nm 98returning a UDP packet from a different IP address than it was 99sent to. 100Note that when specifying IP addresses with 101.Fl h , 102.Nm 103will automatically add 104.Li 127.0.0.1 105and if IPv6 is enabled, 106.Li ::1 107to the list. 108.It Fl i 109.Dq Insecure 110mode. 111Allow calls to SET and UNSET from any host. 112Normally 113.Nm 114accepts these requests only from the loopback interface for security reasons. 115This change is necessary for programs that were compiled with earlier 116versions of the rpc library and do not make those requests using the 117loopback interface. 118.It Fl L 119Allow old-style local connections over the loopback interface. 120Without this flag, local connections are only allowed over a local socket, 121.Pa /var/run/rpcbind.sock . 122.It Fl l 123Turn on libwrap connection logging. 124.It Fl s 125Cause 126.Nm 127to change to the user daemon as soon as possible. 128This causes 129.Nm 130to use non-privileged ports for outgoing connections, preventing non-privileged 131clients from using 132.Nm 133to connect to services from a privileged port. 134.El 135.Sh NOTES 136All RPC servers must be restarted if 137.Nm 138is restarted. 139.Sh FILES 140.Bl -tag -width /var/run/rpcbind.sock -compact 141.It Pa /var/run/rpcbind.sock 142.El 143.Sh SEE ALSO 144.Xr rpcbind 3 , 145.Xr rpcinfo 8 146