> 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?
>
> /Magnus N�slund
It does not give the programs it runs any information about the
client, like ip-address etc. It does not log connections. It does not
offer any access-control features. It may have a built-in unconfigurable
max-limit as to how many programs it will run per minute or second.
It may call listen() with a too low tcp connection backlog number.
--
Gjermund Sorseth
