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