Commit Graph

36 Commits

Author SHA1 Message Date
solsTiCe d'Hiver
e912499c77 Fix explanation in README.md for non arch user
* The file is already installed as `/etc/sysusers.d/kodi-standalone.conf` so it is just needed to edit it. No need to copy it
2022-01-17 08:03:42 -05:00
graysky
5e44c88522 Fix-up services and Readme
* remove depracated WINDOWING= from all services
* fix kodi-gbm.service
* call out wayland dependency
2021-07-20 08:08:05 -04:00
graysky
33dc37310f x86_64: update for kodi.bin[1]
1. 50afcc355a (diff-3e341d2d9c67be01819b25b25d5e53ea3cdf3a38d28846cda85a195eb9b7203a)
2021-07-13 17:40:05 -04:00
graysky
546b6863a4 supply empty file for environment variables 2021-05-23 06:38:08 -04:00
graysky
3df443604c Ubuntu: update sysusers.conf for render group 2021-05-08 09:22:57 -04:00
graysky
44ed658e1b add files for Arch ARM
streamline maintenance of Arch ARM packages/single source of files
2021-04-03 09:05:25 -04:00
graysky
1d7662994d update README with shutdown/reboot best practices 2021-01-30 11:25:30 -05:00
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
graysky
80d6d44698 Revert "Consistent behavior on a systemctl stop vs reboot"
This reverts commit 34515c3338.
2021-01-03 08:27:01 -05:00
graysky
ff58330ee4 Add note to README
https://lists.freedesktop.org/archives/systemd-devel/2020-December/045814.html
2020-12-24 06:20:09 -05:00
graysky
1ddecd1ea1 Add Makefile 2020-12-18 21:34:31 -05:00
graysky
34515c3338 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-16 13:32:25 -05:00
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
graysky
2c5da1a438 support passing environment vars to service 2020-09-14 15:34:44 -04:00
graysky
e6a3e23ff6 expand on ARM warning, fixes #18 2020-08-08 06:43:04 -04:00
graysky
762e312b0b update readme for wayland merge 2020-05-14 06:55:31 -04:00
graysky
aa83f6cc27 fixes #14 2020-05-05 05:56:44 -04:00
graysky
d2cb656955 recursively set ownership on /var/lib/kodi/ to allow any uid/gid 2020-01-14 10:07:11 -05:00
Jan Hicken
6ebf24b1d5 Use systemd-tmpfiles and systemd-sysusers 2020-01-05 12:55:02 +01:00
nl6720
92036950d8 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-12-04 07:57:36 -05:00
graysky
ec902b8f97 fixes #9 2019-05-07 15:07:19 -04:00
graysky
566e8425b3 updates for gbm service 2019-04-29 12:00:25 -04:00
graysky
9df8992d96 fixes #6 2018-08-25 11:16:36 -04:00
graysky
6c4563e281 update readme 2018-06-25 09:10:06 -04:00
graysky
59b8ad7ab3 add license 2018-01-12 08:38:37 -05:00
graysky
bfa43577d6 fixes #4 2017-08-28 16:17:52 -04:00
graysky
3d75368cc7 copy/paste error into readme, fixes #3 2017-05-28 13:51:11 -04:00
graysky
8ff0521e76 update readme 2017-03-09 14:59:53 -05:00
graysky
c649070acf update to run on vt1 2017-03-04 08:46:48 -05:00
graysky
cf7043f813 note modsetting/some AMD drivers re: Xwrapper.conf 2017-02-22 16:31:08 -05:00
graysky
4c9f9d0261 dep 2015-05-27 16:53:54 -04:00
graysky
1f2f807a5e update readme 2015-01-04 17:13:47 -05:00
graysky
900077d3de serivce no longer requires /etc/X11/Xwrapper.config 2015-01-04 15:27:57 -05:00
graysky
cb6e8d8e84 rename unneeded workaround and updates 2015-01-03 10:03:16 -05:00
graysky
181026cbf5 update readme 2015-01-01 13:33:28 -05:00
graysky
5409acb198 first commit 2014-11-05 15:24:29 -05:00