after more than one day:

content of drift-file:
-146.690

Am I correct in assuming that the creation of ntp.drift is not essential to the clock fix anyway? it's just showing you how much the drift is?

Yeah. Don't worry - it caught me too.

I edited ntp.conf to point to /psp/ntp.drift

$ cat /var/lib/ntp.drift
-173.784

Does this beta fix the local widget problem described in:

http://forum.chumby.com/viewtopic.php?id=4380

chumby:~# cat /psp/ntp.drift
-173.025
chumby:~# ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
+dns2.iseek.com. 202.83.64.3      3 u  441 1024  377   36.132   -0.618   0.800
+ntp.central-dat 203.161.12.165   3 u  438 1024  377   68.995  -15.002   0.459
-ns.creativecont 202.83.64.3      3 u  325 1024  377   33.890  -50.413  12.518
*pond.thecave.ws 18.26.4.105      2 u  702 1024  377   71.548    8.920   0.031

DonnaG, the drift isn't harmful as long as the actual time reported in apps matches up with the rest of the world... I think they just wanted to measure that to see just how far off the internal clock gets over time.  The NTP refresh keeps correcting for that drift on a daily basis.

28.March!

and if time and date is adjustet with NTP it will automatically be set.

why do you switch earlier over there? <hehe> not just to jump much earlier into summer <hehe>

ah...thanks.

here (in germany) every year 2time there is a discussion because there is no effect for energy visible.
for me i just would let summertime (because of more daylight in the evening) and delete wintertime.

The chumby will automatically switch between standard time and daylight saving time based on the timezone files that were included in the firmware at the time of that firmware release.

However, there are typically 5 to 10 updates to the timezone files per year, more frequently than we update firmware, so it's possible that some zones might not transition if a region doesn't give sufficient notice.  In almost all cases this isn't a problem since most municipalities give ample notice, on the order of years, before a change actually takes effect.

The most notable exception is Australia, which has several states that change their timezone rules very frequently, often with extremely short notice, so many embedded devices have difficulties.