From 546138910d96f4767ad718eb23ccb0cd115dc370 Mon Sep 17 00:00:00 2001 From: wiz Date: Sat, 19 Jan 2002 03:14:33 +0000 Subject: [PATCH] Drop some unnecessary .Pp, sort sections and SEE ALSO. --- usr.sbin/inetd/inetd.8 | 42 +++++++++++++++++++----------------------- 1 file changed, 19 insertions(+), 23 deletions(-) diff --git a/usr.sbin/inetd/inetd.8 b/usr.sbin/inetd/inetd.8 index f49bdbf5a2e3..5253d65d4dec 100644 --- a/usr.sbin/inetd/inetd.8 +++ b/usr.sbin/inetd/inetd.8 @@ -1,4 +1,4 @@ -.\" $NetBSD: inetd.8,v 1.36 2001/03/16 08:19:13 fair Exp $ +.\" $NetBSD: inetd.8,v 1.37 2002/01/19 03:14:33 wiz Exp $ .\" .\" Copyright (c) 1998 The NetBSD Foundation, Inc. .\" All rights reserved. @@ -371,7 +371,6 @@ word .Dq internal should take the place of this entry. .Ss Internal Services -.Pp .Nm provides several .Qq trivial @@ -425,7 +424,6 @@ creates a file .Em /var/run/inetd.pid that contains its process identifier. .Ss libwrap -.Pp Support for .Tn TCP wrappers is included with @@ -443,7 +441,6 @@ and for access control facility configurations, as described in .Xr hosts_access 5 . .Ss IPsec -.Pp The implementation includes a tiny hack to support IPsec policy settings for each socket. A special form of the comment line, starting with @@ -472,7 +469,6 @@ logs an error message using .Xr syslog 3 and terminates itself. .Ss IPv6 TCP/UDP behavior -.Pp If you wish to run a server for IPv4 and IPv6 traffic, you'll need to run two separate process for the same server program, specified as two separate lines on @@ -531,19 +527,12 @@ explicit remote host access list. .It Pa /etc/hosts.deny explicit remote host denial of service list. .El -.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.) -.Pp -.Dq tcpmux -on IPv6 is not tested enough. .Sh SEE ALSO +.Xr hosts_access 5 , +.Xr hosts_options 5 , +.Xr protocols 5 , +.Xr rpc 5 , +.Xr services 5 , .Xr comsat 8 , .Xr fingerd 8 , .Xr ftpd 8 , @@ -551,12 +540,7 @@ on IPv6 is not tested enough. .Xr rlogind 8 , .Xr rshd 8 , .Xr telnetd 8 , -.Xr tftpd 8 , -.Xr hosts_access 5 , -.Xr hosts_options 5 , -.Xr protocols 5 , -.Xr rpc 5 , -.Xr services 5 +.Xr tftpd 8 .Rs .%A J. Postel .%R RFC @@ -615,6 +599,18 @@ In November 1996, libwrap support was added to provide internal tcpd-like access control functionality; libwrap is based on Wietse Venema's tcp_wrappers. IPv6 support and IPsec hack was made by KAME project, in 1999. +.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.) +.Pp +.Dq tcpmux +on IPv6 is not tested enough. .Sh SECURITY CONSIDERATIONS Enabling the .Dq echo ,