NOTE! This site uses cookies and similar technologies.

If you not change browser settings, you agree to it.

I understand

Welcome, Guest
Username: Password: Remember me

TOPIC: systemd config causes early network termination

systemd config causes early network termination 7 months 4 weeks ago #1

  • Heijnis
  • Heijnis's Avatar
  • Offline
  • Fresh Boarder
  • Posts: 3
  • Karma: 0
I've encountered an issue while developing an addon to control Domotica.
In this case, when kodi is shutdown, the lighting should return to a normal state.
The code executed, needs to contact the domotica system to set the lights.
However, when the exit code is run, in most cases (on very rare occasions not) the network is not available anymore.
I beleive that "after=network.target" needs to be added to the systemd kodi.service configuration file (or maybe another one, I'm not 100% sure).
Network.target is specifically meant to ensure proper shutdown order, and should not be confused with waiting for the network on kodi startup.
I've verified my theory by issuing a "sysctl stop kodi" command on the command line of openelec, and in this case the addon functions properly on kodi exit.

Anyone agree/disagree with this theory?

If correct, do I need to file a bug report to get this fixed?
The administrator has disabled public write access.