[systemd-devel] Input on a systemd service for kodi and strangeness with permissions on /dev/null (systemd 229)

[John]

> From: Mantas Mikulėnas <grawity at gmail.com>
>To: John <da_audiophile at yahoo.com> 
>Cc: Systemd <systemd-devel at lists.freedesktop.org>
>Sent: Tuesday, March 29, 2016 1:22 AM
>Subject: Re: [systemd-devel] Input on a systemd service for kodi and strangeness with permissions on /dev/null (systemd 229)
> 
>Those actually look like typical permissions that a /dev/tty* device would have, so my guess would be that xinit (or something) first sets its stdout to g-w (0600) on startup, to avoid being disturbed, and later tries to set it back to g+w (0620) without actually checking whether its stdout is still a tty...
>


If that is to be expected, perhaps I need a different ExecStop= line.  I am out of ideas.  

1) Anyone care to propose something to the existing service?[1]
2) If my service is not sane, I am open to hear from the experts modifications/total rewrite.

Thank you.

1. https://github.com/graysky2/kodi-standalone-service/blob/master/init/kodi.service