>> Yea, I have the same conclusions. Maybe just a toy NTP client that >> compared one peer or refclock to the sysclock? Then compare that to what >> the local ntpd thinks about the sysclock. > No, because, agauin, that's not far short of the real thing.
There is a lot of wiggle room in "toy client". The starting point would be send a request and print out stuff from the response. That could evolve into a replacement for ntpdate and/or ntpdig. Once it sends and receives well formed packets, it can turn into a traffic generator and/or collect statistics. -- These are my opinions. I hate spam. _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
