5 Commits

Author	SHA1	Message	Date
Lennart Poettering	1193c11a04	units: assign user-runtime-dir@.service to user-%i.slice ... This service won't use much resources, but it's certainly nicer to see it attached th the user's slice along with user@.service, so that everything we run for a specific user is properly bound into one unit.	2018-08-03 10:45:31 +02:00
Lennart Poettering	eb748aef4f	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.	2018-08-03 10:42:09 +02:00
Lennart Poettering	d06e8fbce3	units: make sure user-runtime-dir@.service is Type=oneshot ... We order user@.service after it, hence we need to properly know when it finished starting up.	2018-08-03 10:38:49 +02:00
Zbigniew Jędrzejewski-Szmek	a99655b052	man: add a description of user@.service, user-runtime-dir@.service, user-*.slice ... Fixes #9590.	2018-07-20 16:57:50 +02:00
Zbigniew Jędrzejewski-Szmek	a9f0f5e501	logind: split %t directory creation to a helper unit ... Unfortunately this needs a new binary to do the mount because there's just too many special steps to outsource this to systemd-mount: - EPERM needs to be treated specially - UserRuntimeDir= setting must be obeyed - SELinux label must be adjusted This allows user@.service to be started independently of logind. So 'systemctl start user@nnn' will start the user manager for user nnn. Logind will start it too when the user logs in, and will stop it (unless lingering is enabled) when the user logs out. Fixes #7339.	2018-04-25 16:20:28 +02:00