The subject says it all.

I updated a box to ClamAV 0.93.1, but noticed freshclam didn't work afterwards. I had to chown -R qscand:qscand /var/clamav.

and you got the RPM's from??? I looked at Dag's stuff and am not sure that Scott is still using those and I didn't see that version in atomic testing.

Thanks.

From the ASL yum channel.

I normally have to do the following (on RHEL4) after running an update to clamav:

1. Ensure any new .conf files are included (back up old versions first):

2. Check for correct user in conf:

3. Ensure system user matches:

4. Update system to use new settings:

5. Run freshclam to pull in db updates and ensure all settings are correct (it'll throw warnings if not):

6. Ensure qmail-scanner pulls in changes:

7. If all OK, remove old files (keep system tidy ):

This is a useful command to run and watch for a while after an update (just to ensure all is well):

Hopefully this'll help others with problems after a clamav update...

I know the way to fix these things, but I report them here so the rpms can be fixed to take care of these things themselves.

I have reported them here also... In the mean time this is what I do to get clam updates running quickly!

I've just checked a default install and the default user/database owner always seems to be clamav

But that works for me ... e.g. the log file is owned by clamav:clamav.

I have seen things go wrong when upgrading from one version to another -- only a few days ago in fact.

I cured the problem by brute force by removing clamav and clamd using yum then re-installing.

This resulted in the log file being clamav:clamav again but it was and is working, as is freshclam.

But now I know where to look for which user clamav and freshclam needs those files to be be owned by I'm a lot happier and less mystified. Thanks Kalamari!

Faris.

Thanks Kalimari! This helped me a lot!

yess thanks , its work perfect.