178

Unix/Linux 网络时间协议版本3 Network Time Protocol Version 3 (NTP) distribution for Unix systems

Received: from mail.eecis.udel.edu by whimsy.udel.edu id aa00619;
          4 Mar 1998 11:46 EST
Received: (from juha@localhost)
	by samuraj.c3l.tyreso.se (8.8.5/8.8.5) id RAA22304;
	Wed, 4 Mar 1998 17:45:52 +0100
Date: Wed, 4 Mar 1998 17:45:52 +0100
From: Juha Sarlin <[e-mail]>
Message-Id: <[e-mail]>
To: [e-mail]
CC: [e-mail], [e-mail]
In-reply-to: <[e-mail]> (message from Dave Mills on Wed, 4 Mar 1998 10:17:11 EST)
Subject: Re: loopfilter time constant
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII

>>>>> "Dave" == Dave Mills <[e-mail]> writes:

> The intent of the original MAXTC in the reference kernel implementation
> documented in kernel.tar is to vary over he range 0-6 corresponding
> to a poll interval range 2^4 through 2^10.

It hasn't been like that since xntp3-5.90. Perhaps it should be
changed back? Like this:

*** xntp3-5.92a/xntpd/ntp_loopfilter.c.orig	Tue Mar  3 08:02:47 1998
--- xntp3-5.92a/xntpd/ntp_loopfilter.c	Wed Mar  4 17:44:20 1998
***************
*** 205,207 ****
  		interval = 1;
! 	time_constant = min(peer->ppoll, sys_poll) - 2;
  	clock_adjust = 0;
--- 205,207 ----
  		interval = 1;
! 	time_constant = min(peer->ppoll, sys_poll) - 4;
  	clock_adjust = 0;
***************
*** 311,313 ****
  		ntv.maxerror = ntv.esterror + (sys_rootdelay << 2);
! 		ntv.constant = min(peer->ppoll, sys_poll) - 2;
  		ntv.status = STA_PLL;
--- 311,313 ----
  		ntv.maxerror = ntv.esterror + (sys_rootdelay << 2);
! 		ntv.constant = min(peer->ppoll, sys_poll) - 4;
  		ntv.status = STA_PLL;
***************
*** 690,692 ****
  		ntv.status = STA_PLL | STA_UNSYNC;
! 		ntv.constant = sys_poll - 2;
  #ifdef SIGSYS
--- 690,692 ----
  		ntv.status = STA_PLL | STA_UNSYNC;
! 		ntv.constant = sys_poll - 4;
  #ifdef SIGSYS