With the recent change to prefer "clamdscan" and disable "clamd with direct socket communication," the following changes would need to be made on a Fedora system in order to make use of the default clamd Option 1 (run a separate clamd on the machine): 1. The ClamAV-clamdscan entry in amavisd.conf would need to add "--config-file=/etc/clamd.d/amavisd.conf" to the options 2. The commented entry for the old ClamAV-clamd needs the socket changed to "/run/clamd.amavisd/clamd.sock" Option 2 (run a single clamd on the machine): 1. The "amavis" user needs to be added the "virusgroup" group 2. The amavisd.service unit should remove "Wants=clamd" and add "Wants=clamd" 3. Proper access to /run/clamd.scan directory needs to be made Option 1 keeps allows amavisd to use it's own ClamAV config file, but if other services on the machine are using the default clamd, will run two clamd processes. This bug is entered to clarify that the default preference doesn't work out of the box any longer and some discussion may occur as to what is the "best" way forward. Thanks for your consideration.
Hi, thanks for the report. I'm going to do option 1, which is in line with what amavis was already doing. I'll submit an update shortly.
FEDORA-2023-3027d661fa has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-3027d661fa
FEDORA-2023-dc2766d6fd has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-dc2766d6fd
FEDORA-2023-8ce0355811 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2023-8ce0355811
FEDORA-2023-dc2766d6fd has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-dc2766d6fd` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-dc2766d6fd See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-3027d661fa has been pushed to the Fedora 38 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-3027d661fa See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-8ce0355811 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-8ce0355811` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-8ce0355811 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2023-210f3a38ad has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-210f3a38ad
FEDORA-EPEL-2023-210f3a38ad has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-210f3a38ad See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-8ce0355811 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-dc2766d6fd has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2023-210f3a38ad has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.
Can you please build this one in epel7 and epel8 too?
FEDORA-2023-3027d661fa has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.