[Pkg-clamav-devel] Bug#1100396: clamav-freshclam: systemd service is never enabled
Raphaël Halimi
raphael.halimi at gmail.com
Thu Mar 13 10:33:05 GMT 2025
Package: clamav-freshclam
Version: 1.0.7+dfsg-1
Severity: important
Dear developers,
clamav-freshclam's postinst script uses `update-rc.d` and `invoke-rc.d`
commands, which prevents `debhelper` to add the right
`deb-systemd-helper` commands to enable the service (which AFAIK
*should* be done by `update-rc.d`, but for a reason I didn't dig into,
is not).
Intuitively I'd say that the solution is to complete the `update-rc.d`
and `invoke-rc.d` with their `deb-systemd-helper` counterparts in the
maintainer scripts, mimicking what `debhelper` would do.
Another solution would be to simply remove all occurrences of those
calls (including DO_RUN_AS_EVALUATION in the postinst) and let
`debhelper` do its job, since it seems that both the systemd service and
the SysV init script correctly handle the cron case, and the ifupdown
script correctly handles the daemon case (but I'm not sure about the
other combinations).
Or just plainly remove ifupdown, cron and manual methods, letting the
daemon just start when the network becomes available.
Setting the severity as important because it renders the package useless
(the service never starts after the first reboot, so the signatures are
never updated after that), though IMHO it should be set as critical
since, as the signatures would quickly become obsolete, it gives the
user a false sense of security.
This should also IMHO qualify for the fix to be propagated to stable by
a security update.
Regards,
--
Raphaël Halimi
More information about the Pkg-clamav-devel
mailing list