ntpq peers formatting needs floating point for time slots

Gary E. Miller gem at rellim.com
Wed Feb 1 23:49:20 UTC 2017

Yo Hal!

On Wed, 01 Feb 2017 15:11:42 -0800
Hal Murray <hmurray at megapathdsl.net> wrote:

> The printout in ntpq still needs floating point for big numbers.

Since it is a string, maybe send something nicer?  Instead of:

*SHM(1)          .PPS.            0 l    2    8  377   0.0000  -0.0050  0.0015
-clepsydra.labs. .GPS.            1 u   30   64  377  38.3435   3.9124  6.8764

How about:

*SHM(1)          .PPS.            0 l    2    8  377   0.000u  -5.000u  1.500u
-clepsydra.labs. .GPS.            1 u   30   64  377  38.343m   3.912m  6.876m

That might mess up older clients, maybe some sort of mode bit sent to
the server?  Or maybe do the fancy formatting in ntpq?

OTOH, I know some people hate it when units jump like that...

Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
	gem at rellim.com  Tel:+1 541 382 8588

	    Veritas liberabit vos. -- Quid est veritas?
    "If you can’t measure it, you can’t improve it." - Lord Kelvin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 455 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ntpsec.org/pipermail/devel/attachments/20170201/4586924c/attachment.bin>

More information about the devel mailing list