Re: NTP / RTC problem driving me absolutely INSANE!
It sounds like a timezone problem. It could be one or both of two
things:
1) Your hardware CMOS clock is set to something other than UTC or
local time. For Linux, it must be one or the other -- UTC is
preferable.
In Linux as super-user, at the bash prompt type "(export TZ=UTC ;
date ; clock)" (without the quotes, but with the parens).
The three times it prints should be identical and equal to the
present time in UTC. If, as seems likely, you're in GB and "Summer
Time" is not in effect, then it should also be the same as your local
time.
2) Either MacOS or Linux has the wrong timezone. My guess (assuming
you're in GB) is that one or the other is set to BST, even though it
is manifestly *not* summer in the Northern Hemisphere right now.
Hope that helps!
Rick
On Feb 9, 2007, at 7:56 PM, Ananda Samaddar wrote:
Hello everyone,
by now you're probably mostly familiar with the trials and
tribulations I faced moving to a new architecture but there is one
thing that is really annoying me!
I have NTPD running synced to four servers here in the UK and one
in France which works fine. The correct time is shown and
everything's ok. The problem is when I boot to OSX it always shows
the time as being one hour behind and corrects it. Fair enough.
If I then reboot into Debian it shows the time to be one hour
ahead. You'd think that NTP would just correct the time
accordingly. It does but if I'm logged into GNOME which I use as
the desktop it blanks the screen and no matter what I try I cannot
get back to GNOME or a console terminal. If I reboot after OSX and
log into a terminal while I'm using the terminal GDM informs me
that the greeter (the default Etch one) is crashing and changes it
to the old school one from Potato! The only solution is a hard reset.
Reply to: