> This would actually be pretty easy to do, mechanically speaking. The hard question is what you do with this timing information once you have it.
Oh, believe me, cloud scale devops shops know what to do with all the timing information. On Sun, Jul 14, 2019 at 3:19 PM Eric S. Raymond <e...@thyrsus.com> wrote: > > Mark Atwood <fallenpega...@gmail.com>: > > I want to encourage Hal to think of ways of cracking these problems. > > > > Especially the idea of verifying key parts of the state space, even if > > we can't verify it all. > > I wish him the best of luck... > > > And especially if there was a way to usefully log the relative timing > > of various important state transitions. (That is something on the > > wishlist of the AWS NTP Kronos team.) > > This would actually be pretty easy to do, mechanically speaking. The > hard question is what you do with this timing information once you have it. > -- > <a href="http://www.catb.org/~esr/";>Eric S. Raymond</a> > > -- Mark Atwood <mark.atw...@ntpsec.org> Project Manager, https://NTPsec.org +1-206-604-2198 _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
