> I've not had any crashes since Tuesday, came home from work today to find > that clamd had crashed sometime between 5:21am and 8:03am when the next > unofficial sigs update was run. I've looked at the logs and find nothing to > explain it even with verbose logging on. I've removed the spam.ldb file and > it's no longer being downloaded so that kind of leaves that out. Hi, I was wondering how people were getting on with crashes. If anyone is still getting crashes, please look at the following links and were possible post to the bugzilla entry: http://www.clamav.net/bugs https://wwws.clamav.net/bugzilla/show_bug.cgi?id=1370 The last reply from the ClamAV team was a request for using Valgrind: "Could you try running clamd under valgrind on a test box? It will run much slower (several minutes just to start up and reload the database), but it should give an indication to what is wrong. $ valgrind --trace-chilren=yes --log-file=/tmp/valgrind.log --time-stamp=yes /usr/sbin/clamd Then do the same steps that crashed clamd. Even if it doesn't crash attach valgrind.log if it has any entries about errors." Cheers, Steve Sanesecurity