ntpq peers formatting needs floating point for time slots.

[Eric S. Raymond]

Achim Gratz <Stromeko at nexgo.de>:
> > You don't have the asynchronous option either.  The protocol is lockstep and
> > reverse-lookup on an address can cause long client-side stalls. 
> 
> I can already say I just want the IP addresses.  I can get those from
> the (possibly remote) ntpd very fast and send off the reverse DNS lookup
> asynchronously from ntpq.  If I don't get the result fast enough, I just
> leave the IP in the output.  And yes, that means the actual querying of
> ntpd, the processing of the answers and the combination of the output is
> going to happen asynchronously (not necessarily in parallel, but not
> sequential).

If you still think this is desirable, ship Ian Bruene a detailed proposal.
He pretty much owns the ntpq/ntpmon display code now.

One possible technical blocker: I don't know if async DNS lookups are doable
from Python.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

Please consider contributing to my Patreon page at https://www.patreon.com/esr
so I can keep the invisible wheels of the Internet turning. Give generously -
the civilization you save might be your own.