> > I think the actual issue is that package clamav-db contains > both cld and cvd files. ClamAV doc says you should only have > one of the two. What's more, the cld files are empty. So it > seems that something went wrong in the build process. > > Prior to the update my installation had main.cvd and daily.cld. > After the update it had two additional files, > daily.cld.rpmnew and main.cld.broken, both empty. So it seems > the new clamav-db package brought along two spurious empty > files daily.cld and main.cld. > > > renamed the file main.cld.broken and eventually pulled > everything from > > clamav servers > > > > then had to actually start clamd > > I just removed daily.cld.rpmnew and main.cld.broken and > started clamd. Freshclam had already taken care of the rest. > But may be because I always run freshclam as a daemon, not as > a cron job. > > HTH > Tilman
we run freshclam as a cron job and you are right, there was a CVD error too... so we have two .broken files so to speak main.cld.broken and main.cvd.broken so there was simple conflict of some sort. i tried to copy and paste the errors yet forgot to save it ill check if i can find in the logs and of course, after two manual freshclam runs, we were good to go then manual service clamd start and up :-) thanks again! - rh _______________________________________________ users mailing list [email protected] http://lists.repoforge.org/mailman/listinfo/users
