Re: ntpq peers formatting needs floating point for time slots.

On Fri, Feb 03, 2017 at 04:24:58AM -0800, Hal Murray wrote: > > I just pushed a fix. Please test. > > I bumped the width from 78 to 79. If that screws up, we should document a > test case. I'm assuming the output supports an 80 character line. > > There was a space-space before the delay col

FWD: Go API for monotonitc elapsed time measurements

[From the leapseconds list - good background on timekeeping in go] This is an interesting proposal for fixing the Cloudflare leap second bug, so that time interval calculations do sensible things even when the clock is reset, without making an incompatible change to the existing APIs. https://git

Re: ntpq peers formatting needs floating point for time slots.

Yo Hal! On Fri, 03 Feb 2017 04:24:58 -0800 Hal Murray wrote: > I just pushed a fix. Please test. After 30 seconds of testing, works for me. RGDS GARY --- Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 977

Re: ntpq peers formatting needs floating point for time slots.

I just pushed a fix. Please test. I bumped the width from 78 to 79. If that screws up, we should document a test case. I'm assuming the output supports an 80 character line. There was a space-space before the delay column. I grabbed one of them. Those 2 extra spaces let me change the widt