You may also be running out of randomness...
thymine # cat /proc/sys/kernel/random/entropy_avail
4096
If this number is zero or very low...that could be your
problem. /dev/random blocks if there's not enough
randomness.../dev/urandom does not.
a shot in the dark...
Chad P.
--
Cyrus Home
On Mon, 2006-03-27 at 09:33 -0800, Kevin McWilliams wrote:
> OK, that makes sense. I still don't understand why the timer is reset
> after each attempt to login.
are you sure it is? the timer only runs for an idle connection. if the
subsequent attempts quit cleanly, they won't affect the connect
>> Is there a reason I can't change the timeout to be less than 10 minutes
>> @ pop3d.c:407? Say 3-5 minutes?
>
>The reason you perhaps *shouldn't* do that is that it would violate RFC 1939:
>
>"A POP3 server MAY have an inactivity autologout timer. Such a timer MUST be
>of
>at least 10 minutes'
-- Kevin McWilliams <[EMAIL PROTECTED]> is rumored to have mumbled on
23. März 2006 09:03:37 -0800 regarding pop3 connection timeout & lock
problem:
Is there a reason I can't change the timeout to be less than 10 minutes
@ pop3d.c:407? Say 3-5 minutes?
The reason you perhaps
I have a question about the timeouts on pop3 connections. It looks like
the code doesn't allow for a timeout less than 10 minutes. This causes a
problem with some of my users who are connecting via dial-up or some
other slow network connection. If they login and then lose their
connection to the se
