From: Lennart Poettering <lennart@poettering.net>
Date: Thu, 6 Aug 2020 21:33:29 +0000 (+0200)
Subject: units: order systemd-user-sessions.service after home.mount
X-Git-Tag: v247-rc1~443
X-Git-Url: http://git.ipfire.org/?p=thirdparty%2Fsystemd.git;a=commitdiff_plain;h=bbac7da2b379dfe951db23278ebe8a728ecce7a5

units: order systemd-user-sessions.service after home.mount

This should make /home as automount work reasonably well.

If /home is an automount this has little effect at boot, because if the
automount is not triggered it doesn't matter how the associated mount is
ordered.

It does matter at shutdown however, where home.mount is likely active
now. There the ordering means we'll end sessions first, and only then
deactivate home.mount.

Fixes: #16291
---

diff --git a/units/systemd-user-sessions.service.in b/units/systemd-user-sessions.service.in
index 6d585eb0a15..13de728b1db 100644
--- a/units/systemd-user-sessions.service.in
+++ b/units/systemd-user-sessions.service.in
@@ -10,7 +10,7 @@
 [Unit]
 Description=Permit User Sessions
 Documentation=man:systemd-user-sessions.service(8)
-After=remote-fs.target nss-user-lookup.target network.target
+After=remote-fs.target nss-user-lookup.target network.target home.mount
 
 [Service]
 Type=oneshot