systemd --user support files

* adds a sway-session.target that binds to graphical-session.target
  (see man systemd.special)
* also adds a 10-systemd script that should (must?) be included from sway
  that starts imports the sway environment variables into the systemd
  --user instance, and then starts sway-session.target

The idea is that, any --user units that are wanted by either
sway-session.target or graphical-session.target will be started when
sway runs, and will have the correct environment from sway too.
This commit is contained in:
Дамјан Георгиевски 2019-01-21 23:56:52 +01:00
parent 410c961388
commit 510aafca75
4 changed files with 29 additions and 0 deletions

View file

@ -0,0 +1,7 @@
[Unit]
Description=sway compositor session
Documentation=man:systemd.special(7)
BindsTo=graphical-session.target
Wants=graphical-session-pre.target
After=graphical-session-pre.target