I did a fresh install of Debian 12.4 on my laptop a few days ago. After installing clamav package I noticed that clamav-freshclam.service was running, but "systemctl status clamav-freshclam.service" command reported it as disabled (more precisely: "disabled; preset: enabled"). After reboot, the service was not running (i.e. it was not started automatically).
I could reproduce the same behavior in a virtual machine (also with fresh install of Debian 12.4). After running "systemctl status clamav-freshclam.service" in the virtual machine, the service was automatically started after reboot. However, if I remember correctly, with older versions of Debian Stable I never had to manually enable this service, and after installing clamav and clamav-freshclam packages the service would always start automatically after every reboot.
Just wanted to check if this is expected behavior or perhaps some issue with configuration on my side (although, as I wrote, this happened on two fresh installs - in the virtual machine I did not make changes in any config file before installing clamav package) or maybe an issue with the way how clamav-freshclam package is installed?
I could reproduce the same behavior in a virtual machine (also with fresh install of Debian 12.4). After running "systemctl status clamav-freshclam.service" in the virtual machine, the service was automatically started after reboot. However, if I remember correctly, with older versions of Debian Stable I never had to manually enable this service, and after installing clamav and clamav-freshclam packages the service would always start automatically after every reboot.
Just wanted to check if this is expected behavior or perhaps some issue with configuration on my side (although, as I wrote, this happened on two fresh installs - in the virtual machine I did not make changes in any config file before installing clamav package) or maybe an issue with the way how clamav-freshclam package is installed?
Statistics: Posted by tomac — 2023-12-29 19:09 — Replies 0 — Views 10
