How to Backup Tuner Configuration?

[kalpikos]

Re: How to Backup Tuner Configuration?

Are your flashing the same Image or a different image?

I flashed my box with the same image (openpli4) but newer version (new drivers).

Ussualy when reflash an image you must answer one question if you want bakup setings or not but but if not find why not instal from ts plugin ?

The openpli image doesn't has the option of restoring settings.
I had created a backup from the menu but I didn't try to recover the settings from it.
I tried to recover the settings manually but without success.

It's a little diferent in enigna2 and the file where is stored the settings of the sattelites is the "settings" in etc/enigma2 ,..... when the box reboots everything is gone...
I mean that when I edit the file "settings" in enigma2 folder Im sure that I did it, but when I reboot the box, all changes that I made in this file are gone and the "settings" file is as it was before the editng.

Did you check if entries "config.Nims.*" in file /etc/enigma2/settings are actually the one you saved ?
Just to know if these entries have been successfully restored but they have no effect on tuner configuration.

I copy/paste only this part of settings with "config.Nims"
but after the reboot I can see the changes that I did.

[aplok]

Re: How to Backup Tuner Configuration?

hello,

It's a little diferent in enigna2 and the file where is stored the settings of the sattelites is the "settings" in etc/enigma2 ,


more precisely, is it in :

etc/enigma2

or

/etc/enigma2

or

/var/etc/enigma2

?

..... when the box reboots everything is gone...

on my dm500 e1, /etc/... is read only, ie not writable, as it is in the ram-flash stuff

however, the /var/etc/... is writable, and i can save it for next boot ( as it is since ever)

thefore, i am afraid you try to edit and change file on those versatile part of the directories where data disapear at shutdown,

then, i suggest to have a look on the contents and the differences between /etc and /var/etc

[kalpikos]

Re: How to Backup Tuner Configuration?

Somewhere I read that if I want to do a change in etc/enigma2/settings I have to stop enigma first.
This can be done by using in telnet the commands: init 4 and init 3

Can you confirm this?

[aplok]

Re: How to Backup Tuner Configuration?

... init 4 and init 3
Can you confirm this?

... i have to investigate this ...

on the mean time, can you test this inoffensive recipy:

touch /var/etc/.dont_restart_enigma

killall enigma

or

kill -9 pid

ps aux |grep enigma | awk '{print "kill -9 " $1}'


and check if enigma is still restarting ..

at the end, you can

rm /var/etc/.dont_restart_enigma

[aplok]

Re: How to Backup Tuner Configuration?

... enigma first. ... init 4 and init 3
Can you confirm this?

hello,

--- how to inhibit enigma

no
because i do not have your scripts
those scripts who define the processes ( as services, daemon and enigma )
for level 3 and level 4

however this question is valuable
as it lightens the trigger of enigma
and consecutively, how it comes that enigma process restarts when killed

simply because enigma is a process
launched from an infinite while loop
inside the trigger process

this enigma trigger process is the key of the enigma eternal life immunity

if you suspend this trigger process,
ie if this while loop is broken
enigma is not started by the trigger

elementary, my dear Watson
isn't it


0. so long, we need now to identify which process (and subsequent script) restart enigma when killed

here are clues to find it

this process P :
- is still running
- is parent of enigma process ( E)
- <genuinely>, has a lower process id (pid) of E

so, if i invoke

ps aux

i get

root@dreambox:/var/etc> ps aux
  PID  Uid     VmSize Stat Command
    1 root        540 S   init
    2 root            SWN [ksoftirqd/0]
    3 root            SW< [events/0]
    4 root            SW< [khelper]
    5 root            SW< [kblockd/0]
    6 root            SW  [pdflush]
    7 root            SW  [pdflush]
    9 root            SW< [aio/0]
    8 root            SW  [kswapd0]
   10 root            SW  [cifsoplockd]
   11 root            SW  [cifsdnotifyd]
   12 root            SW  [mtdblockd]
   14 root        540 S   init
   15 root        552 S   /bin/sh /etc/init.d/rcS
   23 root            SW< [fe_thread]
   32 root            SWN [jffs2_gcd_mtd1]
   55 root        592 S   /sbin/inetd
  130 root        520 S   /sbin/httpd -h /var/www -p 81 -c /var/etc/httpd.conf
  156 root        444 S   /bin/gdaemon
  157 root       8528 S   /bin/enigma
  158 root       8528 S N /bin/enigma

where i read that an likely parent process is

/bin/sh /etc/init.d/rcS

ie

/etc/init.d/rcS

which, when readonly vimmed

vim -R /etc/init.d/rcS

or when grepped

grep enigma /etc/init.d/rcS

ie

root@dreambox:/var/etc> grep -n enigma /etc/init.d/rcS
80: cp /var_init/tuxbox/config/enigma/enigma.conf /var/tuxbox/config/enigma
96: if [ ! -d /var/tuxbox/config/enigma/terrestrial ]; then
97: mkdir /var/tuxbox/config/enigma/terrestrial
99: if [ ! -d /var/tuxbox/config/enigma/cable ]; then
100: mkdir /var/tuxbox/config/enigma/cable
154:[ -e /var/bin/enigmanet ] && /var/bin/enigmanet
174:[ -e /var/tuxbox/start_enigma ] && /var/tuxbox/start_enigma
182:rm /var/etc/.dont_restart_enigma
183:touch /tmp/.enigma
184:while [ -e /tmp/.enigma ]
186: if [ ! -e /var/etc/.dont_restart_enigma ] ; then
188: /bin/enigma
190: echo "enigma returned with "$ret
194: rm /tmp/.enigma
199: rm /tmp/.enigma
206: rm /tmp/.enigma



where i read

188: /bin/enigma

eureka : the /etc/init.d/rcS process trigs enigma at line :188



i need then to study this script
to see what to do to inhibit temporarily the immune enigma ...

enjoy !

[kalpikos]

Re: How to Backup Tuner Configuration?

Dear aplok

You give me informations that I can't understand.
All these that you write are very complicated and hard for a simple user to understand it.

I just made a question about the commands init 4 and init 3 and if the stopping of the enigma make enable the editing of the file: etc/enigma2/settings.

[aplok]

Re: How to Backup Tuner Configuration?

hello,

ok, some comments

init 4 and init 3

init command interrupts/starts some processes
to make linux running with a reduced/augmented set of processes
for maintenance (for example) purpose

those command are specifiic to each linux distro
according of the content of the related scripts

consequently, we need to read those script
to find where their instructions start/stop/whatsoever on enigma

make enable the editing of the file: etc/enigma2/settings.

1. check if etc/enigma2/settings is read only, read write
2. then, according to the story you tell us, those settings seemed to be locked, and overwritten on shutdown, or on boot
3. the key is to know why ie : which process, when (boot, shutdown, ...) and where (which script)

4. and last but not least,
to invent such a investigation with hands on enigma2 (i have e1 ... )