ntpclient on Mstar not working please help

[roadrunner]

I put Vlads Oscam on my UE40D57 Mstar and it works very fine. Problem is that Oscam needs 4Min to start. I think it because the time of Oscam is false. The WebIF of Oscam says 00:00 Jan.1970
I put the file samyGOoscam and ntpclient that I have compiled on linux in the Oscam directory, give them 755 but time still wrong even if I try to start ntpclient manualy it says 00:00 Jan.1970
Hope somebody helps with working ntpclient for D series MSTAR.

Thank you

[FilipeAmadeuO]

Use this command line:
/mnt/opt/privateer/usr/bin/oscam/oscam -c /mnt/opt/privateer/usr/bin/oscam/ -w 0 -b

The "-w 0 b" tells oscam not to wait for time info as and also to run on background

[roadrunner]

My Oscam is in /mtd_rwdata/oscam so I edit the command line but nothing happens then I even try edit the samygoOscam file like this:

BIN_OSCAM=${DIR_OSCAM}/${OSCAM} -w 0 -b

Unfortunately still 4,15 Min to start Oscam.
I just saw that ShellCommander also needs 4minutes to start. Right after ShellCommander Oscam also starts after 1sec.

[zoelechat]

So it's not related to ntpClient nor oscam, it's just that your root takes 4min to start

[roadrunner]

I thought root starts with samygo?
56sek after I pressed the power button on the remote control I get the message Samygo started all applications . Then it takes 3 minutes more until Oscam starts . That is why I am surprised that it takes so long to start Oscam.
Is that normal?

[zoelechat]

You probably have some startup script(s) taking too long to start (such as nfs/samba...), try to disable them or rename oscam script to an earlier number (such as 05_...)

[roadrunner]

@zoelchat you were absolutely right!!!
I stoped most of the startup scripts and now Oscam starts in 55sec!

@zoelchat THANK YOU SOOOOO MUCH!!!!!

With a smarthub_closer.so for mstar I'd be totally happy