> If you have can put an accurate time on when clamd stopped > responding, would it correspond to their being a virus DB update?
I don't think so. > I assume that you do automatic updates and this is signalled > to clamd (probably via freshclam --daemon-notify). That's true, I am doing automatic updates and it doesn't seem to be the problem. Although clamd is responding to any commands, it is not able to actually scan the messages anymore. There are still entries in the log file which refer to virus DB updates (just the scanning is not working anymore). So, I assume the threads are dead, but clamd itself is still functional. This happened today morning again, and the only thing I can do is to "killproc clamd" and restart again. Regards, Phil. ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
