Don't run fixtivotime? :DQuote:
Originally Posted by zollymonsta
I don't...
Printable View
Don't run fixtivotime? :DQuote:
Originally Posted by zollymonsta
I don't...
Heh.. but, from memory, when it made the daily call it set the time incorrect once again.
Hmmm, it shouldn't... the daily call tells it to synchronize with the NTP server at 127.0.0.1, which of course will just time out (or sync with an NTP daemon on the tivo itself, but unless you've installed one it won't be there).
Okay... firstly I do not run fixtivotime (hehe... need one of those Internet thingies for that :)) but I do notice a couple of things wrong in the above output. Firstly the daylight saving setting should be 1 as we are in DST rather than 0... and secondly you are running at a 0 offset from GMT, which is incorrect... it should be 43200.Quote:
Originally Posted by zollymonsta
I would suggest you check your postcodezones file to make sure it is in the correct format (can use the dos2unix command to correct this) as follows:
That should fix up the offset problem (should display an offset of 43200) but not sure how to fix the daylight saving recognition. You might like to check that you have the zone info file installed (/var/hack/zoneinfo/Pacific/Auckland).Code:dos2unix postcodezones
ahh thanks thomson... tried that, but it said segmentation fault.
However, I looked at it via the joe editor and it appears there were ^M at the end of line (stupid notepad on windows).
Removed those and resaved and now I get the appropriate output. (see below) So, it was obviously seeing I was in Auckland timezone, but couldnt do the rest because of the invalid characters... first time it's caught me out.
Our postcode is 02115. Found matching timezone Pacific/Auckland
Offset 46800 for timezone NZDT, daylight saving is 1
Connecting to time server 207.126.98.204
t was 3305833438 from server
t is now 1096891438
Time is 2004-10-04 12:03:58
Time set to: Mon Oct 4 12:03:58 2004
Have a nice day.
Time set to: Mon Oct 4 12:03:58 2004
Have a nice day.
Hmm, so you're syncing via NTP and the guide data is OK? We may want to add this set of steps to the setup instructions and set the emulator to dish real NTP addys...
I have loadguide runnning via a cronjob on my other TiVo, which seems to do the same thing once it's run (connects to remote time server and syncs time up) and I've had no problems with time and the guides. Will confirm this tonight.
I'll also check the TiVo on the emulator now that that's working and see if it's still ok with the guide data.
Yep, TiVo and TiVo guide data is fine after doing this.
If it can't be done when connecting to the emulator, it could be added manually via a cronjob each day?
Cron is probably the best solution for now. If I point the emulator ntp setting to a real ntp server, 63 tivos will suddenly be 12 hours off. ;-) Perhaps if we generate a NZ image (as discussed in the guide section today) we could set it up with these TZ files installed and config'd, and once critical mass is reached flip the switch...
Ok.. Sounds like a plan stan (er, Ed) :)
fixtivotime via cron it is for now.