Contributed by mbalmer on from the we-are-at-it-again dept.
Theo added the concept of timedelta sensors, sensors that provide an offset (the error) of the local clock to the reference clock and I threw in udcf(4), a device driver to decode the Swiss HBG and the German DCF77 time signal stations. But until yesterday, we had no way to feed these timedelta sensors to OpenNTPD.
Henning changed the OpenNTPD code to use timedelta sensors, but he had to rescan the list of available sensors peridically, a not-so-elegant design, we concluded. So my idea was to link timedelta sensors to the hotplug event queues: As timedelta sensors can appear or disappear at runtime, aren't they pretty much hotplug devices? Hotplug devices create events in the system that applications can receive. The idea is simple: When a timedelta sensor is added to the system, e.g. after a driver received the first complete time information from a receiver, it generates a hutplug event which OpenNTPD receives. OpenNTPD then rescans the available timedelta sensors and begin using them. Michael Knudsen implemented it and we now have support for timedelta sensors in OpenNTPD.
Of course we still lack GPS support at the moment, but be assured, it will not be long anymore till you will see a commit message and a report here that outlines how addded GPS support to OpenBSD...
(Comments are closed)