sshd buildup of CLOSE_WAIT leading to unable to function
Fri Apr 11 16:08:00 GMT 2014
The interesting detail is it would always stop at exactly 64 sockets
open; which is the maximum number for which select() doesn't have to
spawn a second thread.
Problem disappeared. Given the traces I got the reproduction would
involve somebody's deranged trojan SSH scanner.
64 to too low for Fail2Ban to prevent disaster so I didn't bother. The
fools aren't getting in anyway. I turned off password auth.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin