Document inetd.conf's per-interface binding (new verbage from der Mouse's netbsd mods).

1 files changed, 32 insertions, 2 deletions

diff --git a/usr.sbin/inetd/inetd.8 b/usr.sbin/inetd/inetd.8
index 22375be9abf..f39311d2432 100644
--- a/usr.sbin/inetd/inetd.8
+++ b/usr.sbin/inetd/inetd.8
@@ -30,7 +30,7 @@
 .\" SUCH DAMAGE.
 .\"
 .\"     from: @(#)inetd.8	6.7 (Berkeley) 3/16/91
-.\"	$Id: inetd.8,v 1.3 1997/05/30 07:56:08 deraadt Exp $
+.\"	$Id: inetd.8,v 1.4 1997/06/18 03:01:42 denny Exp $
 .\"
 .Dd March 16, 1991
 .Dt INETD 8
@@ -102,6 +102,28 @@ server program
 server program arguments
 .Ed
 .Pp
+For Internet services, the first field of the line may also have a host
+address specifier prefixed to it, separated from the service name by a
+colon.  If this is done, the string before the colon in the first field
+indiciates what local address
+.Nm
+should use when listening for that service, or the single character
+.Dq \&*
+to indicate
+.Dv INADDR_ANY ,
+meaning
+.Sq all local addresses .
+To avoid repeating an address that occurs frequently, a line with a
+host address specifier and colon, but no further fields, causes the
+host address specifier to be remembered and used for all further lines
+with no explicit host specifier (until another such line or the end of
+the file).  A line
+.Dl *:
+is implicitly provided at the top of the file; thus, traditional
+configuration files (which have no host address specifiers) will be
+interpreted in the traditional manner, with all services listened for
+on all local addresses.
+.Pp
 The
 .Em service-name
 entry is the name of a valid service in
@@ -161,7 +183,7 @@ or continue processing connections on the socket.
 If a datagram server connects
 to its peer, freeing the socket so
 .Nm inetd
-can received further messages on the socket, it is said to be
+can receive further messages on the socket, it is said to be
 a
 .Dq multi-threaded
 server, and should use the
@@ -273,6 +295,14 @@ is reread.
 creates a file
 .Em /var/run/inetd.pid
 that contains its process identifier.
+.Sh BUGS
+Host address specifiers, while they make conceptual sense for RPC
+services, do not work entirely correctly.  This is largely because the
+portmapper interface does not provide a way to register different ports
+for the same service on different local addresses.  Provided you never
+have more than one entry for a given RPC service, everything should
+work correctly.  (Note that default host address specifiers do apply to
+RPC lines with no explicit specifier.)
 .Sh SEE ALSO
 .Xr comsat 8 ,
 .Xr fingerd 8 ,