Re: Multiple Clock Sources Cannot Be Synchronized

See rfc documents or ntpd's design doc, it's determined by root
distance, so if 65ms error doesn't bother you, you can config your
server to report larger root distance so the client would not mark
them as falstickers

chengyechun <[email protected]> 于2024年10月25日周五 09:14写道：
>
>
> Thank you for your reply. There is another question. What is the difference between two clock sources to make them trust each other? After all, the difference of 65 ms can be ignored in some scenarios.
> -----邮件原件-----
> 发件人: Miroslav Lichvar <[email protected]>
> 发送时间: 2024年10月24日 21:29
> 收件人: [email protected]
> 主题: Re: [chrony-users] Multiple Clock Sources Cannot Be Synchronized
>
> On Thu, Oct 24, 2024 at 01:02:40PM +0000, chengyechun wrote:
> > MS Name/IP address         Stratum Poll Reach LastRx Last sample
> >
> > ======================================================================
> > =========
> >
> > ^x 9.82.178.244                 10   2    17     1  +3788ns[+3788ns] +/-  147us
> >
> > ^x 9.82.165.239                 10   2    17     1    -65ms[  -65ms] +/-  152us
>
> These two sources don't agree with each other. They are about 65 milliseconds apart. chronyd doesn't know which one (if any) is correct. That's why normally is recommended to have at least three sources. You can mark one with the "trust" option to force chronyd to select it.
>
> --
> Miroslav Lichvar
>
>
> --
> 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]
>
>

-- 
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]