| Re: [chrony-users] refclock lock max offset |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
On Tue, Nov 20, 2018 at 12:10:04PM +0100, Nuno Gonçalves wrote:
> https://git.tuxfamily.org/chrony/chrony.git/tree/refclock.c#n538
>
> It is a maximum of 0.2s, but can be significantly less when dispersion is high.
>
> There are GPS chips with much higher offset variance, which leads to
> pulses being ignored.
What value would work for you?
We could use a larger value or make it configurable, but I think it
might make it more likely for pulses to be incorrectly paired with
seconds, causing 1-second jumps.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.