retroarch-standalone-service/init/kodi-wayland.service
graysky 847b6ec656 better ExecStop to cleanly exit fixes #23 and #24
Direct call to kodi-xxx in ExecStart= allows direction of kill signal to that
rather than to kodi-standalone wrapper.  This allows the kill signal to hit
the indented executable.  As well, using killall in the ExecStop= allows for
synchronous stopping and for kodi to do shutdown housekeeping tasks such as
saving settings, stopping services (web, zeroconf, etc.) and unloading things.
2020-10-24 14:52:18 -04:00

22 lines
671 B
Desktop File

[Unit]
Description=Kodi standalone (Wayland)
After=remote-fs.target systemd-user-sessions.service network-online.target nss-lookup.target sound.target bluetooth.target polkit.service upower.service mysqld.service
Wants=network-online.target polkit.service upower.service
Conflicts=getty@tty1.service
[Service]
User=kodi
Group=kodi
EnvironmentFile=-/etc/conf.d/kodi-standalone
PAMName=login
TTYPath=/dev/tty1
Environment=WINDOWING=wayland
ExecStart=/usr/bin/cage -- /usr/lib/kodi/kodi-wayland --standalone
ExecStop=/usr/bin/killall --user kodi --exact --wait kodi-wayland
Restart=on-abort
StandardInput=tty
StandardOutput=journal
[Install]
Alias=display-manager.service