Re: [ntp:questions] How common is LI=3 (clocks not synchronized)?

On Fri, Feb 03, 2017 at 09:09:51AM -, William Unruh wrote: > Those pool sources you probably would want to blackball. No. The leap alarm is normally declared when a server has just been restarted, and is not yet synchronized; I'd give it some time to settle down and then retry (say,

Re: [ntp:questions] How common is LI=3 (clocks not synchronized)?

On 2017-02-03, Miroslav Lichvar wrote: > On 2017-02-03, Jakob Bohm wrote: >> On 03/02/2017 04:15, Robert Scott wrote: >>> When the two LI bits come back as 11 (clocks not synchronized) I have >>> been treating that as a fatal error for that server. I

Re: [ntp:questions] How common is LI=3 (clocks not synchronized)?

On 2017-02-03, Jakob Bohm wrote: > On 03/02/2017 04:15, Robert Scott wrote: >> When the two LI bits come back as 11 (clocks not synchronized) I have >> been treating that as a fatal error for that server. I ignore that >> packet and do not attempt to retry my query for that

Re: [ntp:questions] How common is LI=3 (clocks not synchronized)?

Jakob Bohm wrote: On 03/02/2017 04:15, Robert Scott wrote: I am writing some parsing code for reading Time Server packets. The first 32 bits of the returned packet are: +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |LI | VN |Mode |Stratum| Poll |

Re: [ntp:questions] How common is LI=3 (clocks not synchronized)?

On 03/02/2017 04:15, Robert Scott wrote: I am writing some parsing code for reading Time Server packets. The first 32 bits of the returned packet are: +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |LI | VN |Mode |Stratum| Poll | Precision|

[ntp:questions] How common is LI=3 (clocks not synchronized)?

I am writing some parsing code for reading Time Server packets. The first 32 bits of the returned packet are: +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |LI | VN |Mode |Stratum| Poll | Precision|