Referring to https://forum.directadmin.com/showthread.php?t=52195
It would appear the startup scripts for freshclam don't create the PID folder correctly, and when repaired manually it disappears during reboots.
The verified workaround is:
This will show freshclam as running correctly - otherwise it will spam the admin continuously about being down once every 1~2 hours. But needless to say the package should handle this, not the admin
It would appear the startup scripts for freshclam don't create the PID folder correctly, and when repaired manually it disappears during reboots.
The verified workaround is:
Code:
killall freshclam
mkdir -p /var/run/clamd
chown root:clamav /var/run/clamd
chmod -R 775 /var/run/clamd
systemctl start freshclam
service freshclam statusThis will show freshclam as running correctly - otherwise it will spam the admin continuously about being down once every 1~2 hours. But needless to say the package should handle this, not the admin