summaryrefslogtreecommitdiff
path: root/units
diff options
context:
space:
mode:
authorDaan De Meyer <daan.j.demeyer@gmail.com>2023-03-17 13:07:56 +0100
committerYu Watanabe <watanabe.yu+github@gmail.com>2023-03-18 15:05:43 +0900
commitcafd2c0be404cb8879f91d15e05cc8b695b32629 (patch)
treec404b599caf5f66c27e740f174df9c1f1db5b285 /units
parenta9938fb3cb08670f9ff48447d8483d1118344847 (diff)
downloadsystemd-cafd2c0be404cb8879f91d15e05cc8b695b32629.tar.gz
units: Order user@.service after systemd-oomd.service
The user manager connects to oomd over varlink. Currently, during shutdown, if oomd is stopped before any user manager, the user manager will try to reconnect to the socket, leading to a warning from pid 1 about a conflicting transaction. Let's fix this by ordering user@.service after systemd-oomd.service, so that user sessions are stopped before systemd-oomd is stopped, which makes sure that the user sessions won't try to start oomd via its socket after systemd-oomd is stopped.
Diffstat (limited to 'units')
-rw-r--r--units/user@.service.in2
1 files changed, 1 insertions, 1 deletions
diff --git a/units/user@.service.in b/units/user@.service.in
index 0c3440bb3f..41ed55cb1a 100644
--- a/units/user@.service.in
+++ b/units/user@.service.in
@@ -10,7 +10,7 @@
[Unit]
Description=User Manager for UID %i
Documentation=man:user@.service(5)
-After=user-runtime-dir@%i.service dbus.service
+After=user-runtime-dir@%i.service dbus.service systemd-oomd.service
Requires=user-runtime-dir@%i.service
IgnoreOnIsolate=yes