From 56afff50b9e0ccfa16c922c2a8f565ec4f1bbda5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= Date: Wed, 7 Feb 2024 12:43:53 +0100 Subject: [PATCH] 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 | 2 ++ 1 file changed, 2 insertions(+) diff --git a/presets/90-systemd.preset b/presets/90-systemd.preset index 32b68e9f50c..5f1c5b072fa 100644 --- a/presets/90-systemd.preset +++ b/presets/90-systemd.preset @@ -20,6 +20,8 @@ enable getty@.service enable systemd-boot-update.service enable systemd-confext.service enable systemd-homed.service +enable systemd-homed-activate.service +enable systemd-homed-firstboot.service enable systemd-journald-audit.socket enable systemd-network-generator.service enable systemd-networkd.service