Description of problem:
Installing ClamAV from EPEL appears to have multiple issues with generating a functional configuration. Some of the issues include missing systemd configurations, wrong user listed in the config file when compared to what is created in the passwd file. etc..
A good summary of the steps required for a functional configuration after installing from the repository is covered on several blog posts one of which is here: http://linux-audit.com/install-clamav-on-centos-7-using-freshclam/
Version-Release number of selected component (if applicable):
Every time on install
Steps to Reproduce:
1. sudo yum install clamav-scanner clamav-scanner-systemd
2. sudo yum install clamav
3. sudo yum install clamav-update
4. sudo systemctl | grep clam
clamd.scan.service not-found failed failed clamd.scan.service
Opposite of failed. As well as systemd configs for freshclam.
If this is the wrong channel to report an issue like this please let me know. I'm happy to try to report through a more appropriate channel.
Is it safe to assume that the packaging for Clam AV on CentOS 7 will not be fixed?
If so can it just be removed from the EPEL. In it's current packaging state it probably shouldn't have been allowed to be included.
I am not the ClamAV package maintainer, however I try to update the ClamAV
package if a newer version appears. In general ClamAV works for me while
using it with Amavisd-New. Nevertheless I agree with you, that the packaging
of ClamAV is not perfect. On the other hand this requires volunteers on both
packaging and user/testing side - where nobody seems to step up to support
this huge amount of effort in their free time.
I partially disagree with the URL you mentioned, e.g. "Missing systemd
service file" is nonsense, there is a freshclam cronjob doing about the
same. I also disagree with "Change service files", this clearly feels
like the author did not understand how systemd instances work, so please
read "systemd.unit" before following these suggestions about moving and
changing systemd units.
As per clamav-0.99.2-8.el7 the points mentioned should be sorted out,
additionally "systemctl enable email@example.com" should to the same
like the article does by moving systemd unit files wildly around, the
already delivered configuration file is /etc/clamd.d/scan.conf.
TL,DR, clamav-0.99.2-8 is in stable can we close this bug ?
please reopen it if it not fixed .