Topic: Timezone Stuck in California
Under any normal linux operating system setting the timezone to "America/Phoenix" and the timzone_city to Phoenix\tU.S.A.
will allow ntpdate to properly configure the correct local time.
This process works fine on the Chumby One also, but on the CHB Hacker Board it always shows the time as Pacific Standard Time irrespective of the settings in /psp/timezone. This has to be a bug somewhere in how the time is
calculated from the timezone information only on the CHB hacker board not the Chumby One.
I verified that there are no other locations for the timezone file, and tested it with America/Phoenix, America/Chicago, and
even rebooted after changing the timezone file(s) before running ntpdate to be sure everything has a chance to read the
files, and still it stays stuck on California PST time (This is winter) in summer it will probably be PDT or MST I am not sure.
But this is wrong, and I don't know where to begin my search to correct it. Can someone give me a hint where this kind of
bug may be hiding?
Thanks, Barry Mead
The chumby does not utilize the /psp/timezone file to determine the timezone for the ntpdate command. Instead they use
a symbolic link named localtime created in the /etc directory which points to one of the pre-made timezone files in the
/usr/share/zoneinfo directory. These commands fixed my chumby to Phoenix Arizona time.
mount -oremount,rw /
ln -s /usr/share/zoneinfo/America/Phoenix /etc/localtime
mount -oremount,ro /
Now the "ntpdate -u pool.ntp.org" command grabs the time correctly, and the "date" command
shows the proper date and time zone information.
The ntpdate command is assumed to be executed after an internet connection is established of course.