hwclock has life of its own

[Aurel Wisse]

Everything worked fine before I started using ntp. The
system time now is perfectly correct thanks to ntp, 

BUT

When I do "hwclock --systohc", the hwclock is
switching forward one hour after a minute. As follows:
[root@localhost temp]# /sbin/hwclock --systohc
[root@localhost temp]# /sbin/hwclock -r
Sun 26 Jan 2003 04:53:17 PM EST  -0.450474 seconds
[root@localhost temp]# date
Sun Jan 26 16:53:19 EST 2003
[root@localhost temp]# /sbin/hwclock -r
Sun 26 Jan 2003 04:53:22 PM EST  -0.708832 seconds
[root@localhost temp]# /sbin/hwclock -r
Sun 26 Jan 2003 05:54:12 PM EST  -0.181818 seconds


Also, I get:
[wisse@0 16:56:21 ~/temp]$ /sbin/hwclock -r --utc
Sun 26 Jan 2003 12:56:33 PM EST  -0.970221 seconds

which is the wrong way round: I am in the Eastern
timezone and not somewhere in the far east. 

I have:
cat /etc/adjtime:
0.000000 1043617993 0.000000
1043617993
LOCAL

/etc/localtime -> /usr/share/zoneinfo/Canada/Eastern

cat /etc/sysconfig/clock 
ZONE="Canada/Eastern"
UTC=false
ARC=false

cat /etc/sysconfig/clock 
ZONE="Canada/Eastern"
UTC=false
ARC=false

and an iMac Rev. B. Ydl-2.2, kernel: bitkeeper
2.4.21-pre2.

This leads to the following problem: 

Jan 23 22:07:21 localhost ntpd[669]: time correction
of -3601 seconds exceeds sanity limit (1000); set
clock manually to the correct UTC time.

Now, I *could* add ntpdate <server> somewhere at the
end of the boot sequence, but there must be a way to
force the hwclock to the correct time.

Aurel Wisse


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com