Hide Forgot
Description of problem: I am getting repeated errors from cron about freshclam. Version-Release number of selected component (if applicable): clamav-db-0.97-11.el5 clamav-0.97-11.el5 How reproducible: Daily. Steps to Reproduce: 1. rm -f /var/lib/clamav/bytecode.cvd 2. /etc/cron.daily/freshclam Actual results: ERROR: NotifyClamd: Can't find or parse configuration file /etc/clamd.conf Expected results: [empty output] Additional info: I don't use clamd. I use sagator, which can use libclam.so directly and does not need clamd running. Even if I create /etc/clamd.conf, it's still not silent: ERROR: NotifyClamd: No communication socket specified in /etc/clamd.conf ERROR: Can't send to clamd: Socket operation on non-socket I think it's not possible to configure clamd.conf without running clamd to run this quietly. The freshclam.conf can use NotifyClamd paramter to define clamd configuration file, if it's expected. Why are you forcing this parameter in cron.daily/freshclam script?
I agree that it's bad to be overriding clamav's default here of not enabling NotifyClamd, and it's hardly ever needed as clamd should notice when it's db has changed. Also the change should be very safe, since the affected files are tagged config(noreplace), meaning that this change woun't silently happen to the admin. I've fixed this in 0.97-12. Not sure if it's worth pushing this out as an update, or wait until there are more changes.. http://koji.fedoraproject.org/koji/buildinfo?buildID=236711
(In reply to comment #1) > I agree that it's bad to be overriding clamav's default here of not enabling > NotifyClamd, and it's hardly ever needed as clamd should notice when it's db > has changed. Also the change should be very safe, since the affected files are > tagged config(noreplace), meaning that this change woun't silently happen to > the admin. I did this on my server, just all future package updates of cron.daily script will be ignored (saved as rpmnew file). It's good to have this file as config, but it's not a good idea to update it on real systems. > I've fixed this in 0.97-12. Not sure if it's worth pushing this out as an > update, or wait until there are more changes.. > > http://koji.fedoraproject.org/koji/buildinfo?buildID=236711 Please, put it at least to testing. Thank you.
clamav-0.97-12.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/clamav-0.97-12.el6
clamav-0.97-12.el4 has been submitted as an update for Fedora EPEL 4. https://admin.fedoraproject.org/updates/clamav-0.97-12.el4
clamav-0.97-12.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/clamav-0.97-12.el5
Done, now give it some karma :-)
Package clamav-0.97-12.el5: * should fix your issue, * was pushed to the Fedora EPEL 5 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing clamav-0.97-12.el5' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/clamav-0.97-12.el5 then log in and leave karma (feedback).
Seems fine to comment it out, but still change /path/to/clamd.conf to /etc/clamd.conf.
clamav-0.97-12.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.