> The decision to not support inetd was made after qmail 1.03 was > released and > was announced on this list. I assume that the documentation will be > corrected in the next version. I think it is incorrcet to say that djb/qmail does not support inetd anymore. Indeed, even in the new FAQ at ftp://koobera.math.uic.edu/www/qmail/faq/install.html you can read How do I install qmail? Answer: Follow the step-by-step instructions in INSTALL in the qmail package. If you are upgrading from a previous version, use UPGRADE instead of INSTALL. And of course grep -A3 16 /var/qmail/doc/INSTALL 16. Set up qmail-smtpd in /etc/inetd.conf (all on one line): smtp stream tcp nowait qmaild /var/qmail/bin/tcp-env tcp-env /var/qmail/bin/qmail-smtpd The point is that there were many people for whom tcp wrappers did not work out of the box on their redHat 5.0-1 system. This was an error on RH's part, and later the problem got corrected. So then the assumption is that all qmail users subscribe to - and read - every message on this list. Not only that, new users have also gone back and read every message that was ever posted. No, but new users should believe more experienced members on this list when they say tcpserver works better than inetd. Not only that, they should also read the FAQ which gives a hint why one should switch to tcpserver: grep -A2 barf /var/qmail/doc/FAQ 5.1. How do I run qmail-smtpd under tcpserver? inetd is barfing at high loads, cutting off service for ten-minute stretches. I'd also like better connection logging. Mate
