systemd units disabled when calling systemctl daemon-reload
Lennart Poettering
lennart at poettering.net
Tue Dec 12 21:07:12 UTC 2023
On Di, 12.12.23 19:06, Etienne Cordonnier (ecordonnier at snap.com) wrote:
> Hello,
> I am debugging some embedded system running systemd. The behavior I am
> observing is that many systemd targets such as multi-user.target are
> disabled after I run systemctl daemon-reload (as shown by systemctl
> list-units --type target --all). This causes many systemd units to be
> disabled, and forces me to reboot the system.
What do you mean by "disabled"?
in systemd targets can be active and inactive, and that's what
"systemctl list-unit" shows. They can also be enabled/disabled, but
that's what "systemctl list-unit-files" shows. But targets such as
multi-user.target cannot be enabled nor disabled, they are considered
"static", i.e. always enabled if you so will. Which "systemctl
list-unit-file" should actually show.
Hence, I don#t really grok what you are trying to say here...
> Is there a way to debug this systemd target transition? I already
> enabled systemctl
> log-level debug, but I still don't understand why the systemd target is
> changing when I call systemctl daemon-reload on this particular system.
Please state OS, systemd version and provide relevant logs. Otherwise
this is not actionable.
Lennart
--
Lennart Poettering, Berlin
More information about the systemd-devel
mailing list