17 replies to this topic

[microboi37]

Hi, I have an issue with the freq file satellites.xml which keeps returning despite I'm replacing it. The original satellites.xml has ~46KB and is located in /etc/enigma2. There is another satellites.xml in /etc/tuxbox but I seems that it is not used, anyway I replace it too.

 

The problem occurs on different machines, dm800se, dm500hd. On some machines the problem never occurs. I suspect that the problem is power related. When there is a power interruption the box reboots with the original ~46KB satellites.xml loosing the new one.

 

Is this a bug?

 

 

Cheers

[Henkcv44]

After you have replaced the xml file turn off and on the box by means of the switch at the back. If you restart the box the normal way the old xml file is reloaded from the tmp file.

[microboi37]

Is this behaviour by design? How could I make my custom satellites.xml be there without beeing replaced after every restart?

[Henkcv44]

It is not replaced after each restart. Only after the first one. After the hard reset the new xml file is written in the tmp.

[Pr2]

If I am right:

 

- the one in /etc/tuxbox is the one provided by OpenPLi this one can be overwritten after an online update!

 

If you have a custom satellites.xml this one should be placed in /etc/enigma2 and restart the box.

If there is a custom satellites.xml in /etc/enigma2 this one will be used and the other one is ignored.

If /etc/enigma2/satellites.xml doesn't exist than the one provided by OpenPLi is used so the one in /etc/tuxbox.

 

Pr2

[microboi37]

Ok, got it, but after every power loss the 46KB satellites.xml popups from somewhere and replaces my satellites.xml. I did a find -name satellites.xml and found 2 files, the one in /etc/tuxbox and the one in /etc/enigma2 and both are mine - size 240KB. My question is, if I replace them both from where the hell comes the damn 46KB satellites.xml. Is it hardcoded in enigma2?

[Pr2]

Do you use some kind of flash expander of such artifact to get more free space on those STB?

[Rob van der Does]

Never touch the file in /etc/tuxbox as it is a system file, and will be overwritten during an online image update.

The user files resides in etc/enigma2 and has precedence over the system file.

But as with most files: they are kept in RAM so you can never change a file in a live-environment. So first stop Enigma2 ("init 4"), replace the file and start E2 again ("init 3"). Now the user file is active.

[Pr2]

Do you think that the satellites.xml is written back when turning the STB into stand-by?  I don't think so since it is only used during scanning and it is not used for normal operation of the STB.

[Rob van der Does]

Do you think that the satellites.xml is written back when turning the STB into stand-by?

Not when entering standby, but when stopping E2 (properly), e.g. when going to deep standby
 

I don't think so since it is only used during scanning and it is not used for normal operation of the STB.

It is indeed mainly used for scanning, but also for the satellite position for all normal tuning.

 

So yes: the file is read when E2 starts and written when E2 stops.

[nietgiftig]

It is indeed mainly used for scanning, but also for the satellite position for all normal tuning.

 

So yes: the file is read when E2 starts and written when E2 stops.

 

 

 

I use dreamboxedit and the settings (13/19/23/28) from Hans.

In these settings is an satellite.xml with only these satellites.

 

When i look in the /etc/enigma2 there is no satellite.xml. and /etc/tuxbox is the one with the date of the last settings from Hans witch I put in the box this morning (with dreamboxedit). .

 

The strange thing is that I last week had a new dish and LNB's so I had to re-tune 13/19/23/28.

But in the satellites to chose from in the setup for the LNB's were all other positions available while the satellite.xml in /etc/tuxbox only has the 13/19/23/28 satellites .

 

So i think that for part of the setup there must be another list.

[Rob van der Does]

First of all make sure that DBE transfers the satellite.xml to etc/enigma2, not to tuxbox (as that is a system file, and will be overwritten during an online image backup).

 

Secondly: for the newly transferred xml to be effective an E2-restart is required.

 

Apart from the ones in tuxbox & etc there are no other satellite.xml-files.

Edited by Rob van der Does, 3 June 2015 - 20:24.

[nietgiftig]

First of all make sure that DBE transfers the satellite.xml to etc/enigma2, not to tuxbox (as that is a system file, and will be overwritten during an online image backup).

 

Secondly: for the newly transferred xml to be effective an E2-restart is required.

 

Apart from the ones in tuxbox & etc there are no other satellite.xml-files.

 

 

Maybe true, but while installing the new configuration i had the choice of all satellites from west to east, while the the only satellite.xml (in tuxbox) had only 13/19/23/28 in it.

 

So where are the other positions come from?

[Rob van der Does]

I can't say from here; to investigate that you'd need to do it all over again.

But there are only two files and the one in /etc/enigma2 takes precedence over the one in /tuxbox, so it can't be hard to find the culprit (after you restarted E2).

[microboi37]

I have to complain again that the satellites.xml of the size of 45.973 bytes is coming back again from nowhere. Box is dm800se original with the last updates. It's impossible no one has notice this problem yet.

[microboi37]

the file has come back again without updating the box

[microboi37]

sorry my mistake satellites.xml was updating with vhannibal settings

[WanWizard]

The default satellites.xml is in the image, and is under version control. So it will be overwritten everytime you do an update.

 

This is the standard situation:

-rw-r--r--    1 root     root        531573 Jun  6 02:01 /etc/tuxbox/satellites.xml
lrwxrwxrwx    1 root     root            26 Jun  9 19:28 /etc/satellites.xml -> /etc/tuxbox/satellites.xml
lrwxrwxrwx    1 root     root            26 Jun  9 19:28 /usr/share/satellites.xml -> /etc/tuxbox/satellites.xml
lrwxrwxrwx    1 root     root            26 Jun  9 19:28 /usr/share/tuxbox/satellites.xml -> /etc/tuxbox/satellites.xml

You see that /etc/tuxbox is the file that is provided by the image and is versioned, the others are not present by default, and are symlinked to the versioned file.

 

If you have a custom file, you should place it in /etc/enigma2, and it will take precendence over the system file in /etc/tuxbox. If you don't, and overwrite the system file, it will be removed and overwritten with a new system the next time you run an update.