Xref: utzoo comp.protocols.tcp-ip:2076 comp.unix.wizards:5943
Path: utzoo!utgpu!water!watmath!clyde!rutgers!princeton!allegra!mp
From: mp@allegra.UUCP (Mark Plotnick)
Newsgroups: comp.protocols.tcp-ip,comp.unix.wizards
Subject: Re: WARNING: TOD clock not initialized -- CHECK AND RESET THE DATE!
Message-ID: <8321@allegra.UUCP>
Date: 4 Jan 88 05:01:21 GMT
References: <5203@columbia.edu>
Organization: AT&T Bell Laboratories, Murray Hill
Lines: 12
Posted: Mon Jan  4 00:01:21 1988

If anyone has a patch for sun4's, please send it along; we don't yet
have source code or much knowledge of the assembly language.  A
short-term workaround, for both sun3's and sun4's, is to minimize
reliance on the tod clock: run rdate as soon as possible after booting,
and patch the kernel variable dosynctodr to be 0 so that the unix date
is not periodically copied (well, actually, it's adjtime'd) from the
incorrect info in the todr.  This workaround may result in
the unix date running a bit slow due to missed clock interrupts.

    Mark Plotnick
    Department of Solar Calendars
    allegra!mp