Hi Bill; Your email addresses a day of frustration. On Tue, 2006-18-04 at 16:44 -0500, Bill Polhemus wrote: > A few people including myself over the past few weeks asked about problems > with ClamAV, which appeared to "break" after upgrading to FC5. > > The current components for ClamAV 0.88.1 appear to be: > > clamav-0.88.1-1.fc5.i386.rpm > clamav-data-0.88.1-1.fc5.i386.rpm (Contains main.cvd and daily.cvd as of > date) > clamav-devel-0.88.1-1.fc5.i386.rpm > clamav-lib-0.88.1-1.fc5.i386.rpm > clamav-milter-0.88.1-1.fc5.i386.rpm (Contains clmilter) > clamav-server-0.88.1-1.fc5.i386.rpm > clamav-update-0.88.1-1.fc5.i386.rpm (Contains FreshClam) I have everything except clamav-milter -- shouldn't need it. FreshClam works clamscan /FILE works > service clamav restart ]# service clamav restart returns clamav: unrecognized service ]# service clamd restart returns clamd: unrecognized service > and my ClamAV installation was back in action! and mine wasn't > > Hope this is helpful to someone. It is frustrating not to be able to find > an answer to a nagging problem like this--and gratifying when you come up > with the answer. I wanted to share my success. I am glad that you did. clamscan on /home (FC5) has found several virii in my restored /home from FC4. The documentation is terrible. For a program so crucial, I need help. Regards Bill
