On 06/30/2011 07:59 PM, Michael Scheidell wrote: > > > 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?
Depends on how you configured it in /etc/clamd.conf (LogFile vs LogSyslog). > > still watching it. You can try enabling 'DevLiblog Yes' if you want to see warning messages from libclamav in your clamd.log. Best regards, --Edwin _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
