JeroenED/retroarch-standalone-service
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
184e85f6ba
retroarch-standalone-service/init/kodi-x11.service

26 lines
940 B
SYSTEMD
Raw Normal View History

first commit
2014-11-05 21:24:29 +01:00
[Unit]
updates for gbm service
2019-04-29 16:38:00 +02:00
Description=Kodi standalone (X11)
Consistent behavior on a systemctl stop vs reboot If I call systemctl to shutdown or reboot, the effect is that it does not honor kodi-x11.service's ExecStop= line which results in an unclean exit of kodi and of data loss since kodi writes out some data when it exits. By contrast, calling systemctl to stop the service works as expected. It seems systemd treats processes in user.slice differently that those in system.slice and that removing PAMName=login was to blame for kodi's processes running in user.slice. Discussion: https://lists.freedesktop.org/archives/systemd-devel/2020-December/045713.html https://bbs.archlinux.org/viewtopic.php?id=261684
2020-12-14 13:47:28 +01:00
After=remote-fs.target network-online.target nss-lookup.target sound.target bluetooth.target polkit.service upower.service mysqld.service
Improve systemd units Use the same dependencies and their order in both systemd units. Add additional units of services that kodi uses. Don't use "Requires=", kodi can run without a network connection. Export WINDOWING=x11 in kodi.service to skip the autodetection that /usr/bin/kodi-standalone performs. Give kodi-gbm.service the privileges of input group, this allows removing the kodi user from that group's membership since kodi.service does not need it.
2019-10-30 17:32:01 +01:00
Wants=network-online.target polkit.service upower.service
update to run on vt1
2017-03-04 14:46:48 +01:00
Conflicts=getty@tty1.service
first commit
2014-11-05 21:24:29 +01:00
[Service]
remove spaces from service
2016-03-28 15:41:37 +02:00
User=kodi
Group=kodi
support passing environment vars to service
2020-09-14 21:32:22 +02:00
EnvironmentFile=-/etc/conf.d/kodi-standalone
update to run on vt1
2017-03-04 14:46:48 +01:00
TTYPath=/dev/tty1
Improve systemd units Use the same dependencies and their order in both systemd units. Add additional units of services that kodi uses. Don't use "Requires=", kodi can run without a network connection. Export WINDOWING=x11 in kodi.service to skip the autodetection that /usr/bin/kodi-standalone performs. Give kodi-gbm.service the privileges of input group, this allows removing the kodi user from that group's membership since kodi.service does not need it.
2019-10-30 17:32:01 +01:00
Environment=WINDOWING=x11
restore call to kodi-standalone, fixes #26 Calling the kodi-xxx target in ExecStart= was not actually the key to fixing the shutdown bugs in 847b6ec65. Adding the ExecStop= calling killall to the exact target was needed. This commit restores the call to kodi-standalone to allow the "RestartApp" built in to work again and adds the key ExecStop= with killall.
2020-11-08 12:10:38 +01:00
ExecStart=/usr/bin/xinit /usr/bin/kodi-standalone -- :0 -quiet -nolisten tcp vt1
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-10 15:13:36 +02:00
ExecStop=/usr/bin/killall --user kodi --exact --wait kodi-x11
remove spaces from service
2016-03-28 15:41:37 +02:00
Restart=on-abort
StandardInput=tty
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-10 15:13:36 +02:00
StandardOutput=journal
Consistent behavior on a systemctl stop vs reboot If I call systemctl to shutdown or reboot, the effect is that it does not honor kodi-x11.service's ExecStop= line which results in an unclean exit of kodi and of data loss since kodi writes out some data when it exits. By contrast, calling systemctl to stop the service works as expected. It seems systemd treats processes in user.slice differently that those in system.slice and that removing PAMName=login was to blame for kodi's processes running in user.slice. Discussion: https://lists.freedesktop.org/archives/systemd-devel/2020-December/045713.html https://bbs.archlinux.org/viewtopic.php?id=261684
2020-12-14 13:47:28 +01:00
# Without this we will wait the default 90s for this service to go down
# due to xinit staying alive. I don't know of a better way to do this
# without several service files one for the xserver and another for kodi.
# If this bothers you, run kodi-gbm instead which doesn't suffer from this.
TimeoutStopSec=10s
first commit
2014-11-05 21:24:29 +01:00
[Install]
use alias to dm.service rather than target fixes #19 Also see: https://bbs.archlinux.org/viewtopic.php?pid=1131267
2020-07-13 18:57:53 +02:00
Alias=display-manager.service
Reference in New Issue Copy Permalink