I still miss the old behavior of init 4

[birdman]

The old code just halted Enigma without any respect for a proper shutdown.

What old code did this?
init should stop a process by sending it a signal. I can't find which, but I'd expect it to be TERM.
If enigma2 used to just die when sent this than would have been a problem.
If you want to be able to shut down enigma2 quickly without updating config files then the way to achieve that is to define a specific signal that does that when sent. Such as HUP.

[Trial]

Hi,
may be before you joined this board.

Ralf

[Huevos]

What old code did this?

Not sure how long ago. At least 5 years. Code was by Betacentauri.

Problem Tony ViXed was...

Restore a back-up... that writes "/etc/enigma2/settings"... then enigma is shut down... that shutdown writes to the settings file. That was breaking certain complicated tuner configs. Even though before the shutdown the new settings file was loaded into enigma there was some bug in the reload, that has never been found, that the new tuner config from the restore was not properly loaded into enigma... so the write back to the settings file lost some of the data. I think now after a backup restore we just kill the enigma process.

[Huevos]

What old code did this?
init should stop a process by sending it a signal. I can't find which, but I'd expect it to be TERM.
If enigma2 used to just die when sent this than would have been a problem.
If you want to be able to shut down enigma2 quickly without updating config files then the way to achieve that is to define a specific signal that does that when sent. Such as HUP.

Here is the commit...
https://github.com/OpenViX/enigma2/c...050cd51868efa6

[birdman]

Not sure how long ago. At least 5 years. Code was by Betacentauri.

Problem Tony ViXed was...

Restore a back-up... that writes "/etc/enigma2/settings"... then enigma is shut down... that shutdown writes to the settings file.

I reckon the problem with that is the way the code runs.
How I would expect a restore to work is:

1. write a script to do the restore
2. stop enigma2
3. run the script
4. start enigma2 (which will be part of the restore script).

Alternatively, just have a global flag called no_settings_save_on_shutdown, set it and act on it....
Relying on behaviour from an unrelated activity is usually fraught with problems.

[Huevos]

I reckon the problem with that is the way the code runs.
How I would expect a restore to work is:

1. write a script to do the restore
2. stop enigma2
3. run the script
4. start enigma2 (which will be part of the restore script).

Alternatively, just have a global flag called no_settings_save_on_shutdown, set it and act on it....
Relying on behaviour from an unrelated activity is usually fraught with problems.

I like idea 2. Can we look at where that is possible?

With idea 1, if we stop enigma, how do we start the script?

[birdman]

With idea 1, if we stop enigma, how do we start the script?

enigma2 (the binary) is run from enigma2.sh (the script) and the script checks the exit code.
It already checks for a half-dozen or so cases.