On 6/30/11 7:35 AM, Török Edwin wrote:
So the bug is that pthread_cond_timedwait's timeout parameter became invalid.
The patch above does 2 things:
- if pthread_cond_timedwait returns any error (other than ETIMEDOUT) it logs
it, and breaks the loop
- make sure pthread_cond_timedwait's timeout parameter is valid until
pthread_cond_timedwait wakes up
still running 4 hours now.. funny thing.. seems to take half the time
and half the resources of 0.97 or 0.97.1 to run.
(on my 5500 user box, clamdtop would show max of 14 threads by now.. and
top would show 500mb) I only see 4 threads max, and 200mb.)
also, no strange log entries. I assume in /var/log/clamav/clamd.log,
not syslog, right?
still watching it.
still have a 2200 user box with 0.97.1 with the original backedout patch.
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
>*| *SECNAP Network Security Corporation
* Best Mobile Solutions Product of 2011
* Best Intrusion Prevention Product
* Hot Company Finalist 2011
* Best Email Security Product
* Certified SNORT Integrator
______________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.secnap.com/products/spammertrap/
______________________________________________________________________
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
