On Mon, 5 Jun 2000, Magnus Naeslund wrote:
> I run a relatively low traffic mailserver.
> It runs qmail smptd and pop3 from inetd.
> I hear all the time that inetd sucks, but i never hear any reasons why.
> So my question is: why does inetd sucks?
Two that immediately come to mind:
No inbuilt support for access control - it requires a helper program
such as tcpd from the tcp_wrappers program. tcpserver has this built
in.
It has a rate limiting "feature" whereby it will stop servicing a port
for 10 MINUTES if it thinks the rate of incoming connections is too
high (I have flat lined a remote inetd with qmail-remote from a 14k4
modem). tcpserver doesn't care about rate, it just cares about
simultaneous connections.
Inetd will serve UDP connections which is something tcpserver will not.
Regards
Peter
----------
Peter Samuel [EMAIL PROTECTED]
Technical Consultant or at present:
eServ. Pty Ltd [EMAIL PROTECTED]
Phone: +61 2 9206 3410 Fax: +61 2 9281 1301
"If you kill all your unhappy customers, you'll only have happy ones left"
