On Tuesday, 28 November 2017 08:34:22 PST Jason H wrote: > > If you're going to sync time, use NTP. > > It sounds like the best approach is to sync all the clocks independently and > just report events relative to the local clock rather than trying to add a > layer on top, even though the nodes are in direct contact. > https://github.com/bsdphk/Ntimed - says that in 60 seconds, we're accurate > to a few ms, and by 5-10 minutes it can start compensating for jitter in > the crystal.
I'm going to repeat myself: If you're going to sync time, use NTP. Not some other thing that you found on GitHub, especially one whose README says "I am not going to encourage you to do that in production yet", despite it being supported by the LF and the CII. > As for the API: > https://stackoverflow.com/questions/13304672/socket-reading-and-timestamps - > uses recvmsg() > https://github.com/torvalds/linux/blob/master/Documentation/networking/time > stamping.txt - really good guide It looks like Linux will support usec and > even nsec resolution timestamps. Thanks, "SO_TIMESTAMP" is what I was looking for. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
