On Mon, Jun 21, 1999 at 02:26:35PM +0100, Dom Mitchell wrote:
> inetd.conf is one of those things, like newsyslog.conf which is long
> past due for an overhaul...
Some would say the same for inetd. Without wanting to start a flame war,
tcpserver (part of the sysutils/ucspi-tcp port) has some distinct advantages
over inetd:
- Per-service control. Simply use kill -(STOP|CONT) to manage a service, or
even better, use supervise/svc from the sysutils/daemontools port.
- Built-in wrapping support, which scales better because it uses a hashed,
read-only database instead of a textfile.
- Non-privileged users can run servers without root having to edit
/etc/inetd.conf and HUP inetd.
Of course, this only covers TCP-based services.
I'll leave mentioning the downsides to other members of the audience.
--
Jos Backus _/ _/_/_/ "Reliability means never
_/ _/ _/ having to say you're sorry."
_/ _/_/_/ -- D. J. Bernstein
_/ _/ _/ _/
[email protected] _/_/ _/_/_/ use Std::Disclaimer;
To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-hackers" in the body of the message
