On 2013-08-18, Rob <nom...@example.com> wrote: > David Taylor <david-tay...@blueyonder.co.uk.invalid> wrote: >> On 18/08/2013 09:19, Magnus Danielson wrote: > > Perhaps the code should be restructured so that the "network time protocol" > remains part of ntpd, and local reference clocks are moved out into > processes that are more loosely coupled than drivers are now.
They are. The drivers are separate processes. > > A fix like this belongs in a driver for GPS, not in the main code that > supports networking and synchronization of the local clock. Agreed Although it may require knowledge of other sources to fix. It might also be a tinker variable in the driver. > > Only the shared memory interface currently has functionality like this, > and it has some limitations in the information it can convey. If this What limitations bother you? > interface is improved, all the local clock drivers can be moved out > into separate processes and everyone can tinker his driver to fix problems > like this one. It will also be easier to release a fixed driver once > a problem like this suddenly appears. _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions