homed: enable userdb too if homed is requested

Strictly speaking you can run homed without userdb. But it doesn't
really make much sense: they go hand in hand and implement the same
concepts, just for different sets of users. Let's hence disable both
automatically by default if homed is requested.

(We don't do the reverse: opting into userdbd shouldn't mean that you
are OK with homed.)

And of course, users can always deviate from our defaults easily, and
turn off userbd again right-away if they don't like it, and things will
generally work.

diff --git a/units/systemd-homed.service.in b/units/systemd-homed.service.in
index b7b0c3ef1015fde6f9242101bd944a3e76bb0f5b..45dc9306ddabe550d263eeb57456a1a46c5ac31f 100644 (file)
--- a/units/systemd-homed.service.in
+++ b/units/systemd-homed.service.in
@@ -37,3 +37,4 @@ SystemCallFilter=@system-service @mount
 [Install]
 WantedBy=multi-user.target
 Alias=dbus-org.freedesktop.home1.service
+Also=systemd-userdbd.service