units: order user-runtime-dir@.service after systemd-user-sessions.service
authorLennart Poettering <lennart@poettering.net>
Fri, 3 Aug 2018 08:42:09 +0000 (10:42 +0200)
committerThe Plumber <50238977+systemd-rhel-bot@users.noreply.github.com>
Tue, 22 Jun 2021 12:26:51 +0000 (14:26 +0200)
commit1fa9a6bf51a1a1d0fa2ccc23283739d16e9179b4
treed3660153f51c10f787d53a5d0d40bced86d837a9
parent64975b046d5a0877690aa6de9389b8234ee1cfab
units: order user-runtime-dir@.service after systemd-user-sessions.service

We use systemd-user-sessions.service as barrier when to allow login
sessions. With this patch user@.service is ordered after that too, so
that any login related code (which user-runtime-dir@.service is) is
guaranteed to run after the barrier, and never before.

(cherry picked from commit eb748aef4fbfd03b64938aa471bb8ceda1bc89a8)

Related: #1946453
units/user-runtime-dir@.service.in