Re: refclock local
Josef 'Jeff' Sipek <[email protected]>
| Newsgroups | gmane.comp.time.chrony.user |
|---|---|
| Message-ID | <ZNIx559PeDBskwJu@satis> |
On Mon, Aug 07, 2023 at 20:38:23 -0700, Bill Unruh wrote:
> It means that your PPS source is way out of line with the toher two sources
> (half a second different) and thus is an outlier.It has small scatter ( 31us
> rathee than the ms of the others).but still lies well outside the other two
> sources.So chrony is not going to select it and feels that it is not to
> betrusted.
That's the behavior I'd normally expect, but I thought that the 'local'
option on the refclock would behave differently.
From the manpage for convenience:
This option specifies that the reference clock is an unsynchronised
clock which is more stable than the system clock (e.g. TCXO, OCXO,
or atomic clock) and it should be used as a local standard to
stabilise the system clock. The refclock will bypass the source
selection. There should be at most one refclock specified with this
option and it should have the shortest polling interval among all
configured sources.
I understood this to mean:
1. some of the sanity check are skipped (e.g., checking phase alignment
with other sources)
2. the source will be used for *frequency* calculations
3. the source will not be used for *phase* calculations
So, based on these, I expected chrony to report some random but very stable
offset but still make (partial) use of the clock.
Is my understanding wrong?
Thanks,
Jeff.
--
To unsubscribe email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org
with "unsubscribe" in the subject.
For help email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org
with "help" in the subject.
Trouble? Email [email protected]