Subject: Re: bin/20369: inetd can not be "kill"'d in default config
To: Jeremy C. Reed <firstname.lastname@example.org>
From: Martin Husemann <email@example.com>
Date: 02/17/2003 18:11:19
On Mon, Feb 17, 2003 at 08:38:10AM -0800, Jeremy C. Reed wrote:
> That doesn't make sense to me. Running or not running doesn't make any
> difference for adding services. Inetd has to be told to reload for any new
I'm not sure what you are trying to say here.
Yes, we could change the rc.conf default from inetd=YES to inted=NO.
That would add an additional step to enabling inetd based services, where
most howtos just say "add this line to /etc/inetd.conf and send a SIGHUP to
This has been discussed quite some time ago. The result is the current state.
Maby we should re-evaluate that descision, now that the NetBSD way to do
it would be: add this line to /etc/inetd.conf an do /etc/rc.d/inetd status
to check if it's already running, if so run /etc/rc.d./inetd.reload. Otherwise
add "inetd=YES" to /etc/rc.conf and run /etc/rc.d/inetd start.
This is a bit more inconvenient (and more complex). And running an "empty"
inetd does not do real harm.
This is the first time it appeared to me that I was running several of my
machines with inetd enabled but no services served by it.