search for: tcp_ip_abort_interv

...time is allways expired. This is a typical deadlock syndrome. Solutions: 1. tuning TCP stack on Sun box to 35 sec (on linux I don't know how must do it) ndd -set /dev/tcp tcp_rexmit_interval_extra 0 ndd -set /dev/tcp tcp_rexmit_interval_initial 500 ndd -set /dev/tcp tcp_ip_abort_interval 20000 ndd -set /dev/tcp tcp_ip_abort_cinterval 20000 2. Setup the FAILED_CONNECTION_CACHE_TIMEOUT constant - #define FAILED_CONNECTION_CACHE_TIMEOUT 30 /* Seconds between attempts */ + #define FAILED_CONNECTION_CACHE_TIMEOUT 3600 /* One hour, it is enough I think */...

I'm in the process of rolling out new setups with dovecot on CentOS 5.2 and I notice that dovecot doesn't handle the brute-force attacks too nice. I reduced the limit a bit to some reasonable looking value: login_max_processes_count = 32 to stop them earlier and the number of processes stops at that figure when an attack happens. However, it stays at this count for hours although the