shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-12-22 17:35:35 +03:00
Code

user-runtime-dir@.service: don't stop on runlevel switch (#10079)

Browse Source 
Followup to commit 13cf422e04 ("user@.service: don't kill user manager at runlevel switch")

I think there's a general rule that units with `StopWhenUnneeded=yes` need
`IgnoreOnIsolate=yes`...  But it doesn't apply to `suspend.target` and friends.
`printer.target` and friends break on isolate even if we apply the rule[1].
That just leaves `graphical-session.target`, which is a user service.
"isolate" is *mostly* a weird attempt to emulate runlevels, so I decided
not to worry about it for user services.

[1] https://github.com/systemd/systemd/issues/6505#issuecomment-320644819
This commit is contained in:
Alan Jenkins 2018-09-14 04:11:57 +01:00 committed by Yu Watanabe
parent a8a273743f
commit 473b9c683a
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
units/user-runtime-dir@.service.in
View File

@ -12,6 +12,7 @@ Description=/run/user/%i mount wrapper
Documentation=man:user@.service(5)
After=systemd-user-sessions.service
StopWhenUnneeded=yes
IgnoreOnIsolate=yes
[Service]
ExecStart=@rootlibexecdir@/systemd-user-runtime-dir start %i