> This is a surprising report. Since Apache 1.3.x runs separate > server processes, it's kind of surprising that a single client > would stall all server processes. Could you put a debugger on > one of the stalled processes and see where it is? That requires:
1. Being instantly available when slapper hits. 2. Being able to log in and identify the right processes within the Timeout period. On our servers that is 3 minutes. There's usually that much lag just in the time period from alert generated until it hits our pagers. Also, I doubt this is child-related .. all of our servers have hundreds of children, but no server has more than 30 sites. Somehow this attack is choking the accept queue, preventing access to the other unaffected children. -- Joe Rhett Chief Geek [EMAIL PROTECTED] ISite Services, Inc. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
