Charles Elliott
-Original Message-
From: questions-bounces+elliott.ch=verizon@lists.ntp.org
[mailto:questions-bounces+elliott.ch=verizon@lists.ntp.org] On Behalf Of
Terje Mathisen
Sent: Thursday, April 10, 2014 10:21 AM
To: questions@lists.ntp.org
Subject: Re: [ntp:questions] Has anyone th
ursday, April 10, 2014 10:21 AM
To: questions@lists.ntp.org
Subject: Re: [ntp:questions] Has anyone thought about this?
Brian Utterback wrote:
> On 4/10/2014 3:22 AM, Terje Mathisen wrote:
>>
>> The maximum ntpd slew is 500 ppm, which means that the absolute
>> maximum possib
Brian Utterback wrote:
On 4/10/2014 3:22 AM, Terje Mathisen wrote:
The maximum ntpd slew is � 500 ppm, which means that the absolute
maximum possible slew between UTC and the local clock would be 1000
ppm (i.e. the clock is maximally bad, at +500 ppm, and we are
currently slewing at -500 ppm),
On 4/10/2014 3:22 AM, Terje Mathisen wrote:
The maximum ntpd slew is ± 500 ppm, which means that the absolute
maximum possible slew between UTC and the local clock would be 1000
ppm (i.e. the clock is maximally bad, at +500 ppm, and we are
currently slewing at -500 ppm), in which case the max
Dowd, Greg wrote:
However, t1 and t4 are not really in seconds if the client clock is slewing.
That is, the
difference t4 - t1 will be shorter than seconds if the clock is being slowed
down
and larger if the clock is being sped up. Hence the clock slew may be a source
of
variation that is not
4:31 PM
To: questions@lists.ntp.org
Subject: [ntp:questions] Has anyone thought about this?
In ntp_proto.c the delay and offset are computed as follows:
t34 = t3 - t4;
t21 - t2 - t1;
p_del = t21 - t34;
offset = (t21 - t3)/2.;
where t1 = client send time
t2 = server receive
In ntp_proto.c the delay and offset are computed as follows:
t34 = t3 - t4;
t21 - t2 - t1;
p_del = t21 - t34;
offset = (t21 - t3)/2.;
where t1 = client send time
t2 = server receive time
t3 = server send time
t4 = client receive time.
Howe
