[ntp:questions] LOCL clock reachability not 377?

Paul tik-tok at bodosom.net
Wed Jul 30 03:32:31 UTC 2014


On Tue, Jul 29, 2014 at 10:15 PM, Brian Inglis
<Brian.Inglis at systematicsw.ab.ca> wrote:
> As I discovered recently under similar circumstances, offline servers are
> considered
> falsetickers, and if you have insufficient other candidates, or fewer than
> 3, nothing
> gets selected.


I don't think I'm seeing what you're seeing but I could be confused.
I believe I mentioned the same thing last time around on this topic.

ntpd --version;ntpq -pn
ntpd 4.2.7p440 at 1.2483-o Tue Apr 22 11:51:47 UTC 2014 (6)
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
o127.127.22.0    .GPPS.           0 l    2    8  377    0.000   -0.002   0.004
*127.127.1.0     .LOCL.          12 l   65    8    0    0.000    0.000   0.004
 192.168.0.210   .GPS.            1 u   22   32  377    1.304   -0.080   0.028

or just using LOCL ...

     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
o127.127.22.0    .GPPS.           0 l    5    8  377    0.000   -0.005   0.008
*127.127.1.0     .LOCL.          12 l   60    8  200    0.000    0.000   0.008

naturally you need to let NTP discipline your clock and a cold start
requires something to set it.


More information about the questions mailing list