Experimentelle Images/Dateien (stm24)

[apoklyps3]

i know that oscam sometimes crashes, but i am using an older more stable revision wich was running fine on rev.2664. Yestraday on 2669 it stoped at least 5 times and i haven't changed anything in the configuration since i had rev 2664. But i repeat, i will test more today.

[BPanther]

crond seems to be not working at current version of busybox (wont start), but you can make your own crond with a simple script. Maybe i can also rewrite the start script for the check...

[apoklyps3]

so after some testing now i can defenetly tell that oscam crashes alot on the lastest revision. sometimes it only decodes from local as if network isn't working anymore, sometimes it fully shuts oscam down.
changed to v2 tunner but hd channels still don't work on 1W .
yeah...crond seems not working . tryied to start it in telnet and i get this:
crond: NO OPT d!

[BPanther]

Maybe a problem with the highSR (30000) at this programs, but i can not test this position. I'll try this soon at 13°East with Sky Italia (29900).
I hope a fix for the crond will coming soon, or i'll try to fix this by myself.

[BPanther]

Maybe crontab now fixed, so it can be come at the next release.

Code: Alles auswählen

With debug:

ufs910:~# /tmp/busybox crond -f -d 1 -l 0 -c /var/spool/crond
crond: crond (busybox 1.19.0) started, log level 0
crond: user:root entry:*/1 * * * * echo "<- crond is working ->"
111111111111111111111111111111111111111111111111111111111111
111111111111111111111111
11111111111111111111111111111111
111111111111
1111111
crond:  command:echo "<- crond is working ->"
crond: user:root entry:*/1 * * * * echo "<- crond is working ->"
111111111111111111111111111111111111111111111111111111111111
111111111111111111111111
11111111111111111111111111111111
111111111111
1111111
crond:  command:echo "<- crond is working ->"
crond: wakeup dt=50
crond: file root:
crond:  line echo "<- crond is working ->"
crond:  job: 0 echo "<- crond is working ->"
crond: child running /bin/sh
crond: USER root pid 16664 cmd echo "<- crond is working ->"
<- crond is working ->
crond: wakeup dt=10
crond: wakeup dt=50
crond: file root:
crond:  line echo "<- crond is working ->"
crond:  job: 0 echo "<- crond is working ->"
crond: child running /bin/sh
crond: USER root pid 16782 cmd echo "<- crond is working ->"
<- crond is working ->
crond: wakeup dt=10
crond: wakeup dt=50
crond: file root:
crond:  line echo "<- crond is working ->"
crond:  job: 0 echo "<- crond is working ->"
crond: child running /bin/sh
crond: USER root pid 16902 cmd echo "<- crond is working ->"
<- crond is working ->
crond: wakeup dt=10

normal:
ufs910:~# /tmp/busybox crond -f -c /var/spool/crond
<- crond is working ->
<- crond is working ->
<- crond is working ->

[XoXo]

so after some testing now i can defenetly tell that os-cam crashes alot on the lastest revision. sometimes it only decodes from local as if network isn't working anymore, sometimes it fully shuts os-cam down.
changed to v2 tunner but hd channels still don't work on 1W .

Which version of oscam is running on your box? I have no problems at all with ver. 4736 and 1W Kathrein.

[apoklyps3]

i have 4733. are on the latest revision of Bpanter neutrino stm24??

[XoXo]

i have 4733. are on the latest revision of Bpanter neutrino stm24??

Yes. ver. 2669 - both in flash and on USB stick. Try oscam 4736 - it's really stable on Kahtrein.

[apoklyps3]

nice Bpanter. it would be great if crond would work. now all it reamains is to create a script that checks if emu is working and if not to restart. will try to do it myself, but i am not sure i will have success . seems diferent the one in enigma2.
XoXo so is 4733, ran for days in rev 2664. i'll compile later 4736 ,but it doubt will change much.

[XoXo]

XoXo so is 4733, ran for days in rev 2664. i'll compile later 4736 ,but it doubt will change much.

I've downloaded mine (4736) from the aaf E2 server via add-on manager and then transfered it to Neutrino image

[BPanther]

@apoklyps3: crond will have in a later version a option (on/off), standard will be off. And the emu restart maybe a problem while updating the image (not testet), the update needs more than one minute, but emus are disabled for this time.

[apoklyps3]

crond is basicaly created for running jobs in specified time. since some oscam versions tend to shut down on their own (segmentation faults) , we can also make a script that checks if oscam si running and if not it will start. also crond can be set that it runs this oscam-check script every minute.

[BPanther]

I know what you mean, but if the image update starts, all emus will be disabled so i think the crond will restart them after a minute. Fatal on a flash image, because the flash ressources are very limited and also not good on usb image (restoring of settings won't run complete). So i think i must also kill crond if the update starting.

[apoklyps3]

hmmm... you gave me a good ideea. i am going to try to put the latest neutrino in a fresh instalation on USB, rather than as an update. i wanna see if oscam still malfunctions as it does now. anyway, cron is a welcomed feature . thanks for all the hard work

[apoklyps3]

if somebody can test this. on the latest revision #2674 USB-BA with oscam emu:
-yesterday i put the reciever in standby from a FTA HD channel. today when i wokeup and started it, the image was frozen and i was hearing sound , but couldn't change channel or anything, it was like fronzen only that i could see the remote activiy led on the reciver lighting up when i pressed buttons on the remote. only option for me was "restart -f" from telnet. it seems like is the same that happend in other revisions too.