Joe Rhett <[EMAIL PROTECTED]> writes:
> > May I ask, is it just the daemon which happens to handle the worm
> > request which dies? (I presume it is not the parent apache process!) Can
> > you advise on a handy string to search for in the logs to see if we have
> > been getting hit? (We have noticed various intermittent seg faults of
> > apache daemons but thought that this might be due to the race conditions
> > reported in the latest CHANGES log, i.e. 0.9.6g to 0.9.6h).
>
> Not dies, but goes out to lunch. No segv's, but apache becomes
> unresponsive for the virtual host in question. Since the worm scans the
> entire address space, every virtual host becomes unresponsive within the
> space of 20-30 seconds. It stays unresponsive for the configured 'Timeout'
> period.
Joe,
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?
Thanks,
-Ekr
--
[Eric Rescorla [EMAIL PROTECTED]]
http://www.rtfm.com/
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
