diff options
| author | Lennart Poettering <lennart@poettering.net> | 2020-05-28 23:26:24 +0200 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2020-05-28 23:38:29 +0200 |
| commit | 871dc8d644eef7542a5330f84c25b1db2617317c (patch) | |
| tree | 8adff0e0dde48c6f1d7c410dff1859433bca4434 /units/systemd-homed.service.in | |
| parent | a745117dbac02996f7bc13e85d623cb824f39afd (diff) | |
| download | systemd-871dc8d644eef7542a5330f84c25b1db2617317c.tar.gz | |
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.
Diffstat (limited to 'units/systemd-homed.service.in')
| -rw-r--r-- | units/systemd-homed.service.in | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/units/systemd-homed.service.in b/units/systemd-homed.service.in index b7b0c3ef10..45dc9306dd 100644 --- 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 |