Path: utzoo!mnetor!uunet!husc6!hao!ames!ucbcad!ucbvax!bu-cs.bu.EDU!bzs
From: bzs@bu-cs.bu.EDU (Barry Shein)
Newsgroups: comp.protocols.tcp-ip
Subject: WARNING: TOD clock not initialized -- CHECK AND RESET THE DATE!
Message-ID: <8801041745.AA29775@bu-cs.bu.edu>
Date: 4 Jan 88 17:45:43 GMT
References: <5203@columbia.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 17


Oops, I lost the original note so I sent a reply to unix-wizards.
Anyhow, I found that adb'ing the kernel (or via sources) and setting
the variable 'dosynctodr' to zero (it's a flag which defaults to one)
that this problem seems to be ameliorated. I still am not sure what's
causing it or if it's related to the leap-second or not but sections
of the source which slew the clock seem to always check dosynctodr
first.  It shouldn't affect using adjtime from outside the kernel.

I would consider this an emergency patch until someone from Sun sheds
some light on the issue of what's really going on but the systems I've
applied this patch to have been keeping time fine. I'm sure there's
some negative consequence to this patch (always have to set time on
boot? not sure.) I agree tho, I've had systems getting off by an hour
or more of late.

	-Barry Shein, Boston University