ntp

[Patrick Welche <prlw1%cam.ac.uk@localhost>]

I just soldered a replacement SD card reader on my raspberry pi 1 B, and
noticed

ntpq> peers
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 srv146.personal 82.76.255.6      4 u   54   64    1   51.017  5085705   0.004
 ntp.uk.eria.one 85.199.214.102   2 u   53   64    1    9.073  5085704   0.004
 2a03:b0c0:1:e0: .INIT.          16 u    -   64    0    0.000    0.000   0.000
 luna.dh.bytemar 185.203.69.150   2 u   40   64    1   10.014  5085704   0.004
ntpq> peers
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
+srv146.personal 82.76.255.6      4 u   24   64   37   48.636   14.126   6.248
+ntp.uk.eria.one 85.199.214.102   2 u   24   64   37    9.010   -0.058   5.994
 2a03:b0c0:1:e0: .STEP.          16 u    -   64    0    0.000    0.000   0.000
*luna.dh.bytemar 185.203.69.150   2 u   32   64   37   10.115    0.168   5.910


which makes perfect sense, as the pi has no battery to keep a clock going.

My question is why this doesn't happen on amd64? On amd64, if the clock
goes out of sync by that much, e.g., after booting into windows without
having set the "clock is in UTC" registry key, ntpd quits, and one has to
run ntpdate first so that ntpd keeps going. Both /etc/ntp.conf files are
the default identical ones.


Cheers,

Patrick