Am 14.12.20 um 17:22 schrieb John:
Thank you for the reply, Colin. I found that to be the case[1]. I
think everything is working as expected now. I still have quirks with
the kodi-x11.service since it has to call xinit as well as the kodi
binary but I do not know of a cleaner way to do it
Thank you for the reply, Colin. I found that to be the case[1]. I
think everything is working as expected now. I still have quirks with
the kodi-x11.service since it has to call xinit as well as the kodi
binary but I do not know of a cleaner way to do it unless there is a
multiple unit solution
John wrote on 14/12/2020 12:52:
> Note that it looks
> like I will need to add some udev rules to allow the kodi user to
> shutdown the system which it could do when the PAMName=login was
> present.
Just a small hint, but it might be policykit rules you need to add
rather than udev rules.
Col
On Mon, Dec 14, 2020 at 12:39 AM Andrei Borzenkov wrote:
> If your application creates user session, on shutdown systemd will stop
> existing sessions and it happens independently of your service.
Andrei - Thank you for this info. It caused me to search 'systemd
wait for user session on
14.12.2020 05:08, John пишет:
> 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
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.
Does
