Re: [cobalt-users] Pop Server dying

[Gerald Waugh <gwaugh@xxxxxxxxxxxxxxxxxxxxxxx>]

On Fri, 15 Mar 2002, Larry Smith wrote:
> Skeeve,
> 
> INRE [cobalt-users] Pop Server dying:
> > I have a problem where the pop server run out of Inetd is dying
> > frequently...
> > from /var/log/messages
> >  pop-3/tcp server failing (looping), service terminated
> > This is causing a great deal of trouble....
> > I have put a cronjob to restart inetd every 15 minutes... but this thing is
> > dying even faster than that... every 2-3 minutes sometimes... and each time
> > it dies the fones go mad...
> >
> > Any advice on how to fix this?
>
If you see the message "pop3/tcp server failing (looping), service
terminated" in your log, it means that inetd received more requests for
Qpopper service within one minute than it is configured to allow. On most
systems, by default inetd only permits 40 connections within one minute to
any service. If you have a lot of users, this may be too small a limit.  You
can increase the global default (for all inetd services) by passing a
timeout argument to inetd.  On most systems, you can increase the timeout
for Qpopper by modifying your inetd.conf file. Find the pop3 line, and
change "nowait" to "nowait.timeout", for example, "nowait.50" to permit 50
Qpopper connections within one minute.

--
Gerald Waugh