Different Shutdown process from Kodi or ssh

[Nachteule]

(27th Apr, 2020 03:29 AM)Gauner Wrote:  Ok, thank you very much for clarification.
I already opened a issue on github.
I added there my finding about the different ways that the system changes the runlevel when shutdown from Kodi.

Is there a similar folder like /lib/systemd/system-shutdown that executes scripts at startup? Or is my consideration correct, that startup scripts must go into the rc?.d or rc.local, while shutdown scripts go into /lib/systemd/system-shutdown? So, there's no consistent way of executing a script on startup and shutdown?

I've already seen you issue on github

I looked deeper into today and it seems that elogind is the culprit. Can't say if the version is too old (its the version shipped with buster, on giithub are oc newer versions matching with systemd versioning), or if just elogind is wrong configured.

Anyway, I have a test installation running without elogind, using logind from systemd, looks ok so far. Shutdown from Kodi works as expected (AFAIS)

I don't know if there is a startup folder similar to shutdown folder, I would assume there isn't though. And yes, I think you're right to put startup script into rc.local if required or look into file /etc/default/xbmc, variable USERRUN. maybe you can wrote your own userrun script

For a quick test, you can replace /etc/init/elogind.conf with

Code:

description "Enable user and session management by systemd/(e)logind"
author      "mkreisl mkreisl@xbian.org"

env EDAEMON=/lib/elogind/elogind
env SDAEMON=/lib/systemd/systemd-logind

start on started dbus and remote-filesystems
stop on starting rc RUNLEVEL=[06]

respawn

script
    if [ -e $SDAEMON ]; then
        DAEMON=$SDAEMON
    elif [ -e $EAEMON ]; then
        DAEMON=$EDAEMON
    fi
    test -e $DAEMON && exec $DAEMON || { stop; exit 0; }
end script

and install systemd (/lib/systemd/systemd-logind is provided by systemd)