C. Andrews Lavarre wrote: > I agree. I'll report back tomorrow, but it looks like the old > freshclam.log was generating the issue with clam-update. > > I've now nuked all older versions of freshclam and clamscan, cleaned > out the freshclam.log of older entries, still haven't figured out > what is triggering clam-update since it isn't in any .cron directory...
Unfortunately that didn't work, so I checked the files again. clam-update was dated last April. So I nuked it, then reinstalled 0.87.1. Apparently this latest version does not have clam-update, at least I can't find it. And freshclam and clamscan both work just fine. So maybe that is the fix. Cheers, Andy _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
