Date: Mon, 21 Jun 1999 16:02:53 +0200 From: Jos Backus <Jos.Backus@nl.origin-it.com> To: Dom Mitchell <Dom.Mitchell@palmerharvey.co.uk> Cc: David Malone <dwmalone@maths.tcd.ie>, Sheldon Hearn <sheldonh@uunet.co.za>, freebsd-hackers@freebsd.org Subject: Re: Inetd and wrapping. Message-ID: <19990621160253.F36966@hal.mpn.cp.philips.com> In-Reply-To: <19990621142634.A10715@palmerharvey.co.uk>; from Dom Mitchell on Mon, Jun 21, 1999 at 02:26:35PM %2B0100 References: <86080.929966430@axl.noc.iafrica.com> <9906211413.aa28663@salmon.maths.tcd.ie> <19990621142634.A10715@palmerharvey.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
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
_/ _/ _/ _/
Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer;
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990621160253.F36966>