wwortel

@olddog

these are symlinks from different rcN.d directories to the script to be used in /etc/init.d.

It is standard in many linux distributions that, depending on the run level that is used to start the OS and that is the number N, the entries in those directories rcN.d are called that start with S...  and get executed in sorted order by calling the symbolic link with the parameter 'start'. So, to answer your question, it is not repeatedly the script itself with a different name, but they are references to the script that itself is there only once in the /etc/init folder. When you call the link linux will follow the symbolic link and call what it is pointing to.

The number in the naming following that S influences the order of the script calls because of the sorted execution. On exit from a run level a search is done for entries that start with K.... and the links get called with the parameter 'stop'. That is why i modified the script a bit so it can start or stop the python script. In this case stopping the script in a certain way is not critical so those K... links in rcN.d were omitted.

The python script could still be hardened a bit for cases where things do not go as planned (e.g. socket not present, stream not present, webif not present, and the like). But so far have not seen it fail because OpenPli enigma2 and oscam run quite stable.

In case of problems: Python has nice solutions for so called exception handling by use of the try: except: construction. Rather than just issuing a statement like e.g. pipe = os.popen("dvbsnoop .... (that needs several things to be ok in order to give a result) you make it subject to try: and then under except: define what should be done would it fail. Currently in case of an error the python script may give up.

My experiences with installation of the scripts on a Formuler F1 set top box, running OpenPli v4, Aug. 2016 version.
The box runs a mipsel broadcom chip bcm7356, dual core.
A PC was used that is running Linux Debian8.

First a big thank you to the makers of the script and those that helped analyse the problem.

Observations:
* standard oscam can be used.
* the windows application dreamboxEDIT.exe v7.0.1.0, which I tried from Linux via 'wine', cannot set the proper audio pids for the HD channels.
So a manual edit of 'lamedb' is necessary.  
* the address of the socket needs to be changed in the python script
* the capmt operation mode in oscam, standard set to 6 needs to be changed to 0 to have the proper socket arrangement.
 

To start the python script I am using a single and slightly modified script in the /etc/init.d folder.

The relevant files can be found here with some more detailed instructions:

http://dorpstraat.com/27w5/27w5.tar.gz

Not working is streaming from the box while watching a channel.

This would require multiple simultaneous instances of the script and tighter integration into enigma2 to get them properly started.