shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2025-02-02 09:47:03 +03:00
Code

units: Order user@.service after systemd-oomd.service

Browse Source 
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.

(cherry picked from commit cafd2c0be404cb8879f91d15e05cc8b695b32629)
(cherry picked from commit c4848032f132e0cb82c7967e5434378c98111a8c)
(cherry picked from commit 603d8402de93d7ed716dca0ce531deb06928cfc0)
This commit is contained in:
Daan De Meyer 2023-03-17 13:07:56 +01:00 committed by Zbigniew Jędrzejewski-Szmek
parent f9ed8cc70d
commit dce229df23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
units/user@.service.in
View File

@ -10,7 +10,7 @@
[Unit]
Description=User Manager for UID %i
Documentation=man:user@.service(5)
After=systemd-user-sessions.service user-runtime-dir@%i.service dbus.service
After=systemd-user-sessions.service user-runtime-dir@%i.service dbus.service systemd-oomd.service
Requires=user-runtime-dir@%i.service
IgnoreOnIsolate=yes