Roberto C. Sánchez wrote:
On Sat, Jun 09, 2007 at 07:04:51PM +0100, andy wrote:
ZONE_TMP_FILE=`mktemp` && find /usr/share/zoneinfo/ -type f -print0 |xargs
-0 md5sum >>$ZONE_TMP_FILE && grep `md5sum /etc/localtime |cut -f1 -d\ `
$ZONE_TMP_FILE && rm -f $ZONE_TMP_FILE
<SNIP>
4c9f9c5c5f86bcc5465c08831ef59e75 /usr/share/zoneinfo/Europe/London
<SNIP>
Hmm, that is what you thought it was supposed to be set to, correct?
Does your clock program have some sort of settings within the
application for timezone or daylight savings time?
Regards,
-Roberto
Not that I can discern. In the KDE clock settings (accessible as root)
the TZ is always set to Guernsey and identifies itself as BST (British
summer time). As noted previously, the BIOS shows the correct time so it
would seem that somewhere between the BIOS time setting and the loading
of Etch that either the system gains an hour (?), or is switching to UTC
(which might push it forward an hour) or has got its notion of BST
screwed up. However, on my machine all is fine. Go figure! It does have
me stumped!
A
--
"If they can get you asking the wrong questions, they don't have to worry about the
answers." - Thomas Pynchon, "Gravity's Rainbow"
