Stuart Blake Tener wrote:
Bryan, at alia:
I believe I tried restarting both services in different orders and nothing seemed to cause chronyd to use the gpsd data. However, what I suspect might be superlatively helpful to me is if people using chronyd can post their configuration files from /etc/chrony directory.
I can't provide intelligent commentary now; random stupid will have to suffice.
If you are trying to get the chrony socket working on a 64-bit system with both endpoints initially started as uid 0; you should be using /run/chrony.clk.${basename}.sock IIRC chrony.${basename}.sock only works if you have working PPS.
If perversely starting both endpoints not uid 0 move the reference to /tmp with the same name.
SHM would be units 0 and 2 respectively, and could be monitored via ntpshmmon.
