Hi I guess this problem has been dealt with before, but it still seems to keep cropping up.
The above log report is an indication of a failed freshclam update. It is annoying, because it generally means that no updates will work from then on - it doesn't fix itself. It seems to be caused by an old instance of freshclam hanging around. Is there any other cause of this failure? The first time I came across this problem it continued for several days without being noticed, and I didn't think of looking to see if there was an old freshclam instance. At the time I thought I had solved it by simply renaming the ClamAV.update.log so it could start again. What is the best solution to ensure reliable updates without manual intervention? Just ensure that the cron job kills any old instances of freshclam before running a new one? Regards Jim Holland System Administrator MANGO - Zimbabwe's non-profit e-mail service Tel: (263-4)-334111/304471 _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
