Re: [chrony-dev] [GIT] chrony/chrony.git branch, master, updated. 1.25-pre1-18-g20a4340

[Miroslav Lichvar <mlichvar@xxxxxxxxxx>]

On Wed, Apr 13, 2011 at 11:16:48AM -0700, Bill Unruh wrote:
> Adding a constant to the
> distance (assuming this did not change the min_distance) still changes the
> weights in yours (and a lot if sd gets small) .

I meant adding a constant to all distances.

> If you wanted you
> could put in sd+min_distance as the divisor. But this seems the
> wrong thing to do anyway,
> because really the importance of small differences in the distance should
> always remain small. 

Why? A significant part of the distance is static delay corresponding
to the length of the path which the signal has travel through. I just
wanted to remove that from the weight calculation.

> Also, if a server is further away, it IS less reliable. There could be a
> constant offset-- outgoing times being a set amount more than incoming. Ie, if
> a server has a round trip of 1 sec, and another has a roundtrip of 1ms, even
> with the same jitter I would trust the second more.

The selection algorithm takes care of that.

If there is a constant offset, no change in weight calculation will
help. But if the paths are symmetric, we'll track both sources equally
well, no matter how far it is.

-- 
Miroslav Lichvar

---
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.