7 replies to this topic

[rtzhjgg0]

I use to share a central timers.xml between different images. This file is in /media/hdd and is symlinked on each image.
This works perfectly on VTi and BH etc but not on OpenPLi. I can can create the symlink on PLi with

-----------
init 4
rm -rf /etc/enigma2/timers.xml
ln -sfn /media/hdd/timers.xml /etc/enigma2
init 3
-----------

but after a E2-restart PLi overwrites the symlink. Other images don't overwrite the symlink after a E2-restart, but just write correctly the timer differences to /media/hdd/timers.xml
 

How can I avoid overwriting of this symlink in OpenPLi?

[pieterg]

We use atomic writes, to ensure you never end up with a corrupted file.
(Instead, you always have either the old unmodified version, or the new version)

This method does not work when the file is a symlink, it will be replaced by the new file.

[rtzhjgg0]

Ok, I understand


Is there any alternative method/workaround to share timers.xml with other images/boxes?

[WanWizard]

Just curious: why would you want to run timer events on multiple boxes simulaneously? You'll end up with multiple copies of the same recording?

[rtzhjgg0]

Just curious: why would you want to run timer events on multiple boxes simulaneously? You'll end up with multiple copies of the same recording?

Boxes have in my configuration differnt timers.xml:
-all DM8000 flash and multiboot images share they timers.xml in /media/usb
-all Duo2 flash and multiboot images share they timers.xml in /media/hdd

[Pr2]

And since OpenPli doesn't support multiboot... 

[rtzhjgg0]

This method does not work when the file is a symlink, it will be replaced by the new file.

...perhaps a E2-plugin that allows the user to choose a different path for his timers.xml ?

[pieterg]

That sort of thing cannot be controlled by a plugin.
Same as making a workaround, which detects that timers.xml is a symlink, and decides not to use the atomic write + move operation.

And to be honest, I'd rather not make such workarounds, just for a use case like this. (though I understand why it makes sense in your case)
The main goal is a safe and reliable storage of programmed timers, the last thing you want is a corrupted timers.xml...