inetd natively sucks. Get tcpserver from DJB's page.
If you need help setting that up, hit the FAQ, then hit the mailling list
archive, then hit the list if all else fails.
Hope this helps.
Reid Sutherland
Network Administrator
ISYS Technology Inc.
http://www.isys.ca
Fingerprint: 1683 001F A573 B6DF A074 0C96 DBE0 A070 28BE EEA5
-----Original Message-----
From: Brian D. Kohl <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Friday, April 23, 1999 11:32 AM
Subject: inetd-smtp/tcp problem
>Hey all,
>
>So I have a new qmail install here at my new company. Threw out Exchange
>before it was even set up, though after they had paid for it. No worries.
>
>I have Qmail running as it should, been great since last Friday when I set
>it up, but yesterday I had 3 seperate events of the following error (as
>logged in /var/log/messages):
>
>Apr 22 12:02:43 mailsf inetd[256]: smtp/tcp server failing (looping),
>service terminated
>
>This killed everyones ability to connect to our mailserver, and I could not
>telnet to port 25 as well. The problem was not with Qmal, but with inetd
>itself. A kill -HUP on inetd made the problem go away. It happened 3
>times yesterday, but it seemed quite randomly. Hasn't happened again. I
>had maybe 10,000 emails go through the server (a PII 400), so load was not
>an issue (I have another Qmail setup elsewhere doing 50,000 a day via inetd
>- tcpserver is on the plate, but no time yet - not that 50k is alot).
>
>Any ideas what would chop down my port 25 abilities with inetd?
>
>Thanks very much,
>Brian
>
>
>---------------------------------
>Brian D. Kohl
>Chemconnect, Inc.
>415.364.3328
>---------------------------------
>
