Ran into an issue where last night, two of my servers with clamav 101
versions updated to 103.
After the update, the old clam was running, so if you reboot, you find that
clam is not starting. In order to fix:
1) Install clamd
Yum install clamd
2) uncomment the "LocalSocket" in /etc/clamd.d/scan.conf so LocalSocket is
enabled.
3) add clamd to system startup
Systemctl enable clamd@scan
Note: the @scan says to use the scan.conf file in step 2
4) start clamd
Systemctl start clamd@scan
5) enable clamav-freshclam
Systemctl enable clamav-freshclam
Systemctl start clamav-freshclam
6) To check that they are enabled, find them using:
Systemctl list-unit-files | grep enabled
Where this was biting me was my older Centos 7 installations that had the
qmail clamav setups and converted to EPEL clamav.
Carl
P.s. If I missed anything, feel free to correct and post back to the list.
---------------------------------------------------------------------
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
