Bug#995990: systemctl --now flag has no effect in two circumstances
Michael Biebl
biebl at debian.org
Sat Oct 9 22:50:31 BST 2021
Am 09.10.21 um 16:15 schrieb MichaIng:
> Package: systemd
> Version: 232-25+deb9u13
>
> On current Debian Stretch, the systemctl --now flag, when enabling or
> disabling a service, has no effect in those two cases:
>
> 1. The service is already enabled respectively disabled: On newer
> systemd versions (Buster and Bullseye), the service is still started
> respectively stopped, even if the enabled/disabled state does not change.
>
> 2. An init.d service exists: In this case the --now flag has no effect,
> regardless whether the service is currently enabled or disabled. On
> newer systemd versions the presence of an init.d service has no effect
> on that flag.
>
> Tested on a current Debian Stretch x86_64/amd64 system.
Thanks for your interest in Debian.
Stretch is old-old-stable by now and doesn't receive any updates anymore
(aside from maybe security fixes done by the ELTS team.)
As this issue is apparently solved with more recent versions of systemd,
I'm going to close this bug report.
Regards,
Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20211009/f277ac59/attachment.sig>
More information about the Pkg-systemd-maintainers
mailing list