On 23.10.13 00:17, Eric S. Raymond wrote:
awk '
/127\.127\.28\.0/ { sum += $5 * 1000; cnt++; }
END { print sum / cnt; }
' </var/log/ntpstats/peerstats
Should that be .1 rather than .0?
I'm thinking of this coment in ntpshm.c:
* Segments 0 and 1: permissions 0600, i.e. other programs can only
* read and write as root.
*
* Segments 2 and 3: permissions 0666, i.e. other programs can read
* and write as any user. I.e.: if ntpd has been
* configured to use these segments, any
* unpriviliged user is allowed to provide data
* for synchronisation.
*
* As gpsd can be started as both root and non-root, this behaviour is
* mimicked by:
*
* Started as
root: do as ntpd when attaching (creating) the segments.
* (In contrast to ntpd, which only attaches (creates) configured
* segments, gpsd creates all segments.)
*
* Started as non-root: only attach (create) segments 2 and 3 with
* permissions 0666. As the permissions are for any user, the creator
* does not matter.
*
* For each GPS module gpsd controls, it will use the attached ntpshm
* segments in pairs (for coarse clock and pps source, respectively)
* starting from the first found segments. I.e. started as root, one
* GPS will deliver data on segments 0 and 1, and as non-root data
* will be delivered on segments 2 and 3.
This seems to imply that the PPS unit is .1 rather than .0.
This is correct, but I was assuming that the PPS doesn't have to be
fudged, because it is directly connected to the kernel PPS via an
interrupt. I have a fudge offset only on the GPS unit, and none on
the
PPS. This seems to make sense to me, because only the NMEA stuff is
delayed by the RS232 transmission.
Beat