[ntp:questions] LOCL clock reachability not 377?

mike cook michael.cook at sfr.fr
Tue Jul 29 19:52:32 UTC 2014


Rob,

  Looks like a bug anterior to your version. I see the same issue with version="ntpd 4.2.6p5 at 1.2349-o" whether or not there is a preferred local clock or not, and whether or not there are other active server associations.

One for Harlen if it has not already been flagged.

Tue Jul 29 21:32:48 CEST 2014
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 127.127.1.1     .LOCL.           5 l   25   64    1    0.000    0.000   0.008
o127.127.22.1    .PPS1.           0 l    8   16    1    0.000    0.002   0.008
...
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 127.127.1.1     .LOCL.           5 l  300   64   20    0.000    0.000   0.008
o127.127.22.1    .PPS1.           0 l   11   16  377    0.000    0.004   0.008
....
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 127.127.1.1     .LOCL.           5 l  437   64  100    0.000    0.000   0.008
o127.127.22.1    .PPS1.           0 l    4   16  377    0.000    0.004   0.008

<snip>

Le 29 juil. 2014 à 19:14, Rob a écrit :
> This appears to work OK, output from the "ntpq -p" command is now:
> 
>     remote           refid      st t when poll reach   delay   offset  jitter
> ==============================================================================
> oPPS(0)          .PPS.            0 l   14   16  377    0.000    0.000   0.001
> *LOCAL(0)        .LOCL.           5 l   93   64    2    0.000    0.000   0.000
> EXTERNAL SERVER .INIT.          16 u    -  256    0    0.000    0.000   0.000
> EXTERNAL SERVER .INIT.          16 u    -  256    0    0.000    0.000   0.000
> EXTERNAL SERVER .INIT.          16 u    -  256    0    0.000    0.000   0.000
> 
> Good.
> 
> But why is the "reach" of the LOCAL clock 2 and not 377?
> The reach bit cycles up until it is 0, then the LOCAL clock is no longer
> reference clock, the PPS status changes to x
> 
> _______________________________________________
> questions mailing list
> questions at lists.ntp.org
> http://lists.ntp.org/listinfo/questions


More information about the questions mailing list