hi redhatters,

fetchmail has a parameter for timeout, but apparently that parameter
doesn't affect whatever timeout results in exitcode=2, socket error.

i bet the relevant timeout is in the kernel, not fetchmail?

this is happening alot when our dialup is busy with other things, like
rsync, or up2date, or other traffic between lan and internet..

any idea where to cast the tweaking eye?

tia,
greg


-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list

Reply via email to