On Wed, 2009-03-04 at 19:36 +0200, Török Edwin wrote: > As far as I understand the crash occurs when reloading the signatures > (actually when freeing old signatures), > but only if clamd had some load before (i.e. it doesn't crash just by > reloading the signatures on a fresh clamd). > That makes me think this has to do with some memory corruption from > earlier, or is dependent on the timing > of events.
Here is information on my crash of today: Mar 4 02:09:17 localhost clamd[4492]: Reading databases from /var/lib/clamav Mar 4 02:09:17 localhost kernel: clamd[4492]: segfault at 84 ip b7fb5ca6 sp bfca2fb0 error 4 in libclamav.so.5.0.4[b7fab000+b0000] Unofficial sigs update began at Wed Mar 4 02:09:06 CST 2009 - Pause complete, checking for new database files... Two of Steves db's were updated and the MalwarePatrol database. Chris -- KeyID 0xE372A7DA98E6705C
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
