Lou Baccari wrote:
>
> Sorry Pedro I should have mention that the hwclock has always held the
> correct EST time.
Doesn't this mean that Linux is assuming your hw clock is GST...? Hence, the
double timezone shift...? If nothing else works, why not set the hw clock to
GST?
> I changed the time this morning at 8:16 AM EST, and when I just check the
> time the date was 5 hours behind and hwclock command showed the correct EST
> time. The xntp daemon was no longer active. This problem is a pain, any
> other ideas???
The reason xntpd was no longer active is probably in /var/log/syslog (this is
from one of mine today):
Feb 26 13:04:02 homer xntpd[14073]: time error 1007.151614 is way too large (set
clock manually)
...and it was only off by 20 minutes...
Pierre