mirror of
https://github.com/systemd/systemd
synced 2024-07-22 10:44:58 +00:00
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.
This commit is contained in:
parent
a9938fb3cb
commit
cafd2c0be4
|
@ -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
|
||||
|
||||
|
|
Loading…
Reference in a new issue