retroarch-standalone-service/init
graysky 8c5d854a36 back to user.slice
It seems that as long as the Kodi menu is used to call a shutdown or reboot,
the services will allow the application to gracefully exit including saving
settings, uptime etc.  This will only NOT occur if the user calls the box to
shutdown or reboot via a call to systemctl for the reasons cited in previous
commits.

While not optimal, it is consistent with the same thing happening if others
users are logged into the box, working, and a sysadmin calls the systemctl
to reboot.  The result is users will lose work/data.

Going back to the user.slice is better for USB mounts, and for pulseaudio
sessions as well.
2021-01-03 21:15:41 -05:00
..
kodi-gbm.service Revert "Consistent behavior on a systemctl stop vs reboot" 2021-01-03 08:27:01 -05:00
kodi-wayland.service Revert "Consistent behavior on a systemctl stop vs reboot" 2021-01-03 08:27:01 -05:00
kodi-x11.service Revert "Consistent behavior on a systemctl stop vs reboot" 2021-01-03 08:27:01 -05:00
sysusers.conf back to user.slice 2021-01-03 21:15:41 -05:00
tmpfiles.conf better ExecStop to cleanly exit fixes #23 and #24 2020-10-24 14:52:18 -04:00