]> git.ipfire.org Git - thirdparty/systemd.git/commit
preset: enable homed sidecar services
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Wed, 7 Feb 2024 11:43:53 +0000 (12:43 +0100)
committerLuca Boccassi <luca.boccassi@gmail.com>
Thu, 8 Feb 2024 22:44:00 +0000 (22:44 +0000)
commit56afff50b9e0ccfa16c922c2a8f565ec4f1bbda5
tree524e7a6c7af7bd740bb46645b953f940258a9bfc
parent82047a6aa7230031d2a579e81d5f8871c23e0616
preset: enable homed sidecar services

As described in https://github.com/systemd/systemd/issues/31235, the preset
state for systemd-homed-activate.service was unclear. On the one hand, we have
a preset with 'enable systemd-homed.service', and systemd-homed.service has
'Also=systemd-homed-activate.service systemd-homed-firstboot.service', so
'preset systemd-homed.service' would also enable those two services, but
'preset systemd-homed-activate.service' would disable it, because the presets
don't say it is enabled. It seems that this configuration is internally
inconsistent. As described in the issue, maybe systemctl should be smarter
here, or warn about such configs. Either way, let's make our config consistent.

Follow-up for d1f6e01e4743ae94740314eeb46a162112ef4599 and
3ccadbce3358ba1db7ce5fa3f8dd17c627ffd93b.
presets/90-systemd.preset