On 6/30/11 7:35 AM, Török Edwin wrote:
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
so far, so good.
still running.. with the side effect of using a LOT less threads than
0.97 or 0.97.1. also seems to use a lot less ram (doesn't start to use
un non recoverable ram). I assume due to less threads active.
by now, I would have peeked at 14 threads (13 idle, one running stats)
when I looked at it with clamdtop.
now, I have 4 (3 idle and one running stats)
--
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
