Re: XNTP3/MIPS RISCos 5.01 solved (ish)

Article View: comp.protocols.time.ntp

Article #1032

Back to comp.protocols.time.ntp Previous Next

#1032

From: Philip Gladstone
Date: Mon, 25 Jan 1993 16:46

11 lines
992 bytes

The way that SETTIMEOFDAY_DAMAGED works is that is enables (part of)
the SLEWALWAYS code. settimeofday() calls are only done for errors of more than
2 seconds. After a settimeofday, a gettimeofday is done to determine the error
left (which is typically under 1 second - depending on the nature of the
broken settimeofday). This value is pushed into the SLEWALWAYS code. Thus
after a STEP, the system time will *not* be correct, but the internal NTP
time will be. The error is removed by the adjtime calls over some time
period.

Philip

Technical Details

Message-ID: <9301251646.AA07785@cgin.cto.citicorp.com>

Path:

arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!ames!agate!ucbvax!CGIN.CTO.CITICORP.COM!philip

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!ames!agate!ucbvax!CGIN.CTO.CITICORP.COM!philip
From: philip@CGIN.CTO.CITICORP.COM (Philip Gladstone)
Newsgroups: comp.protocols.time.ntp
Subject: Re:  XNTP3/MIPS RISCos 5.01 solved (ish)
Message-ID: <9301251646.AA07785@cgin.cto.citicorp.com>
Date: 25 Jan 93 16:46:37 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 11