Martin Burnicki writes: > Rob wrote: > > Only the shared memory interface currently has functionality like this, > > and it has some limitations in the information it can convey. If this > > 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. > > Once upon a time there was a good proposal for a new SHM interface with > improved features. However, this was not accepted, and the discussion > simply faded out. See: > http://lists.ntp.org/pipermail/questions/2011-March/028913.html
The SHM refclock now supports nanoseconds, as I recall. And I'd be happy to look at these issues for ntp4-5.0 too. How about a bug report that refers to a topic in the Dev web for discussion? H _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions