Page 1 of 1

Satellite == NTP cannot set date

Posted: Wed Feb 25, 2009 2:50 am
by seth_keith
If you have a satellite NTP may not work for you. You can manually edit the ntpdate line inside

/rootfs-ro/etc/rc.d/init/time.pm

Change this line from

# if (system(qq(/usr/bin/ntpdate -b -s "$_")) == 0)

to

if (system(qq(/usr/bin/ntpdate -t 60 -b -s "$_")) == 0)

This gives a 60 second timeout. I have wildblue, most other satellite vendors will cause problems.

Possibly we could get some timeout defaults for high latency connections in minimyth.conf?

I also had problems with the default timeout values in the "myth weather" package....

60 is way too long

Posted: Wed Feb 25, 2009 2:58 am
by seth_keith
60 seconds is wayyy too long, try -t 3 or -t 4 instead for wildblue.

Posted: Wed Feb 25, 2009 6:25 am
by Pablo
Is there some reason that you do not sync the time of your frontend(s) to your master backend?

sync front end to back end time

Posted: Sat Feb 28, 2009 7:02 am
by seth_keith
It sounds good to sync the frontend to the backed time to me, I just wasn't thinking straight ( or possibly reading too much ).

However, I think there are still timeout related networking issues related to the myth weather and the IMDB poster retrieval. More details later...