Re: clock skew

winmute (winmute@lucifer.gv.kotnet.org)
Thu, 4 Jun 1998 01:29:01 +0200


http://www.azstarnet.com/~axplinux/FAQ-1.html#ss1.2
somewhere around there it says:
[start]
Clock seems to be off by 20 years:
This is not really a bug, but many people seem to have problems
with it. Here's Jay Estabrook's Definitive Solution.

ARC console and SRM console keep dates in the time-of-year (TOY) clock
in slightly different formats (actually, only the "year" field differs).

The "/sbin/clock" binary normally expects the format which SRM uses; you can,
however, tell it to expect ARC format instead, using the "-A" flag.
Thus, to read the clock when its kept in ARC format, say "clock -r -A", and
to write it, "clock -w -A". If its not written in the expected format, the
console (ARC or SRM) will prolly complain about it the next time it has a
chance... :-\
[end]
and
[start]
Clock gets set to a random date and time
This occurs on the PC164/LX164/SX164 mainboards. This is due to
a slightly different version of the TOY clock hardware on these
boards. As seen above, your system clock gets set from the TOY
clock during bootup, using clock. To test if your setup has
this problem try the following command:

while true; do /sbin/clock -r [-A]; done

(use the -A option when your hardware TOY clock is in ARC
format)
If you see any inconsistent results, you need to upgrade your
/sbin/clock. Get one of:

gatekeeper.dec.com:/pub/DEC/Linux-Alpha/Kernels/clock-pc164-rh4.2
gatekeeper.dec.com:/pub/DEC/Linux-Alpha/Kernels/clock-pc164-rh50

[end]
ps ; always good idea to read good faq's ;)