In all examples on the Internet "How to configure ClamAV for RHEL/CentOS", there is /etc/clamd.d/clamd.conf file. But in current version (clamav-server-systemd-0.99.2-1.el7.noarch) of EPEL package there is /etc/clamd.d/scan.conf. There is file /usr/lib/systemd/system/clamd for runnnig the daemon and in this file there is .include /lib/systemd/system/clamd@.service where %i to run with various config files: ExecStart = /usr/sbin/clamd -c /etc/clamd.d/%i.conf --foreground=yes This is smart, but very confusing and breaks previous setups with clamd.conf Please use only one file /usr/lib/systemd/system/clamd@.service and use /etc/clamd.d/clamd.conf in this file (as a lot of other services do in RHEL/CentOS). This change will change what BZ #1356507 requires to fix.
Not sure which examples you refer to, however the packaging layout of ClamAV changed between EPEL 6 and 7. Additionally I fear that a single clamd.conf is not enough to serve all use-cases out there, which are more that just a local file scanner. Mentioned bug #1356507 should be fixed per clamav-0.99.2-8.el7.
Hi, also TL,DR, and same question , clamav-0.99.2-8 is in stable can we close this bug ?
please reopen it if it not fixed .