Your message dated Sun, 10 Oct 2021 16:43:39 +0200
with message-id <[email protected]>
and subject line Re: Bug#995990: systemctl --now flag has no effect in two
circumstances
has caused the Debian Bug report #995990,
regarding systemctl --now flag has no effect in two circumstances
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
995990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995990
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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.
Best regards,
Micha
--- End Message ---
--- Begin Message ---
Version: 241-5
Am 10.10.21 um 16:30 schrieb MichaIng:
Upgrading to 241-5~bpo9+1 from Stretch backports btw solves it, though
this is not applicable in all cases, e.g. Raspbian systems where
backports are not available.
raspbian is not maintained by Debian, fwiw.
Anyway, marking as fixed for 241-5
--- End Message ---
