Article View: comp.protocols.time.ntp
Article #1016CLOCK.ADJ
From: Alan Larson
Date: Thu, 21 Jan 1993 21:50
Date: Thu, 21 Jan 1993 21:50
24 lines
1325 bytes
1325 bytes
The loop filter parameters in xntp3 (include/ntp.h) say:
* Loop filter parameters. See section 5.1 of the specification.
* Note that these are appropriate for a crystal time base. If your
* system clock is line frequency controlled you should read the
* specification for appropriate modifications.
#define CLOCK_ADJ 0 /* adjustment interval: 2**0 = 1 */
When I looked in section 5.1 and table 6 (page 40 of RFC1305),
it said that the appropriate value or CLOCK.ADJ was 4 seconds for
a crystal, and 1 second for the mains.
Which is right? There seems to be no way to determine which is
correct, since the section 5.1 (Fuzzbnall Implementation) has no
discussion of why this particular interval was selected.
Interestingly, there is also no mention of a clock adjustment being
actually done at a time relative to the CLOCK.ADJ counter. What is
the real purpose of this variable?
Alan
Technical Details
Message-ID:
<1993Jan21.215057.12347@unet.net.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!elroy.jpl.nasa.gov!ames!pacbell.com!unet!loren!larsonShow Full Headers
Complete Article Headers
Newsgroups: comp.protocols.time.ntp Path: arc1-ca.pugleaf.net!sparky!uunet!elroy.jpl.nasa.gov!ames!pacbell.com!unet!loren!larson From: larson@loren.net.com (Alan Larson) Subject: CLOCK.ADJ Message-ID: <1993Jan21.215057.12347@unet.net.com> Sender: news@unet.net.com Nntp-Posting-Host: loren Organization: Network Equipment Technologies Date: Thu, 21 Jan 1993 21:50:57 GMT Lines: 24