[ On Tuesday, June 6, 2000 at 09:26:56 (-0400), Bill Sommerfeld wrote: ]
> Subject: Re: inetd.conf [sommerfeld@netbsd.org: CVS commit: basesrc] 
>
> If we did things the way you describe, users needing one service will
> start inetd and get everything, and fall victim to a
> bug/misconfiguration in a "normal" service they don't need, didn't
> know about, and don't care about...

Indeed.  I'd rather see inetd running idle and listening on no sockets.
Then users need only follow the tried and true recipe of editing
/etc/inetd.conf and then kicking the already running inetd to get things
going.  Given the new rc.d scheme it might even be "dangerous" to
default "inetd=NO" in rc.conf because then they might start it by hand
(perhaps even without knowing it) but forget to fix it to start on the
next boot too.

-- 
							Greg A. Woods

+1 416 218-0098      VE3TCP      <gwoods@acm.org>      <robohack!woods>
Planix, Inc. <woods@planix.com>; Secrets of the Weird <woods@weird.com>