JeroenED/retroarch-standalone-service
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
6e0aedb13f
retroarch-standalone-service/x86/init/sysusers.conf

27 lines
723 B
Plaintext
Raw Normal View History

recursively set ownership on /var/lib/kodi/ to allow any uid/gid
2020-01-06 21:47:47 +01:00
# override these settings by copying this to /etc/sysusers.d/ and modifying it therein
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
# Type Name ID GECOS Home directory Shell
recursively set ownership on /var/lib/kodi/ to allow any uid/gid
2020-01-06 21:47:47 +01:00
g kodi - -
u kodi - "Kodi User" /var/lib/kodi
# supplemental groups
m kodi audio
m kodi optical
m kodi video
fixes #14
2020-05-01 18:22:56 +02:00
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
# other groups, see: /usr/lib/sysusers.d/arch.conf or basic.conf
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 23:55:15 +01:00
# m kodi network
# m kodi power
# m kodi tty
# m kodi disk
# m kodi storage
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
Ubuntu: update sysusers.conf for render group
2021-04-28 13:00:34 +02:00
# Ubuntu users only
# uncomment the following line if the kodi user needs access to /etc/ttyxxxx
fixes #14
2020-05-01 18:22:56 +02:00
# https://github.com/graysky2/kodi-standalone-service/issues/14
# m kodi dialout
Ubuntu: update sysusers.conf for render group
2021-04-28 13:00:34 +02:00
# uncomment the following line if you're running Ubuntu >=20 since they created
# a new render group of which the kodi user needs to be a member
# m kodi render
Reference in New Issue Copy Permalink