The short answer: it is a very known problem with inetd. The quickest
replacement is using xinetd (the same thing but with a cherry on top :) and you
get extra functionalities if you care.
It isn't by chance that the latest redhat chose xinetd over inetd for the role
of being the Internet Super-Daemon as they call it.
Migration? not a problem, xinetd comes with a script that automagically
converts your current inetd.conf for you (and you might check that new file to
see if you weren't running any unnecessary services along the misty lines of
inetd.conf).
Have fun!
Daniel Fonseca
On 09-Nov-2000 Jev wrote:
>
> Hello all,
>
> Im running an old version of cyrus-imap (v1.5.19) with Aaron Newsome's
> mysql pwcheck patch (ver 0.02). My choice for this was unfortunately
> because it was the only version i could get to use mysql at the time
> (pam_mysql not and still isn't an option) and I was under vicious time
> constraints from management. (the 2.x branch was available at the time,
> plus newer 1.5.x versions)
>
> Anyway, my problem :)
> We are running a web-mail application that was written in-house. There is
> some horrible JS that refreshes in the users browsers every 60 seconds
> (in a small frame on the page) that check mail, with a few people logged
> onto the site the imap servers gets a lot of different checking
> mail.
>
> This would eventually get too much and I get an entry in
> /var/log/messages from inetd reading:
>
> inetd[430]: imap/tcp server failing (looping), service terminated
>
> And I *think* it comes back after a set amount of time (I cannot test
> this because users need their mail *apparently* ;)
>
> So, is this a known issue? I have seen reference that others have used
> this same version under heavy loads. What should I do to track down and
> locate the problem? What other information can I provide?
>
> Before you say it, yes I want to upgrade, but I must fix the system that
> is in place for the short term, then I can concentrate on the newer
> release.
>
> Kind Regards,
> Emil JV. Björsell
>
> --
> http://www.ecad.org/~jev/jev.gpg
> Key fingerprint = D058 2F50 5202 4FC2 7B71 3996 369D 12C2 0F23 67D2
