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

2017-02-01 Thread Gary E. Miller
Yo Eric! On Wed, 1 Feb 2017 23:18:33 -0500 "Eric S. Raymond" wrote: > Hal Murray : > > [I tried to submit an issue, but it was reject as spam.] > > > > Somebody recently changed things to print out a 4th digit. That > > made things worse. It was already broken if you had a negative > > number

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

2017-02-01 Thread Eric S. Raymond
Hal Murray : > [I tried to submit an issue, but it was reject as spam.] > > Somebody recently changed things to print out a 4th digit. That made things > worse. It was already broken if you had a negative number bigger than 1000 > which isn't all that uncommon. Sigh. I'll revert that commit.

Re: ntpq peers formatting needs floating point for time slots

2017-02-01 Thread Gary E. Miller
Yo Hal! On Wed, 01 Feb 2017 16:14:41 -0800 Hal Murray wrote: > Your version of "nice" conflicts with mine. I'd love to see what you can come up with. RGDS GARY --- Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Ben

Re: ntpq peers formatting needs floating point for time slots

2017-02-01 Thread Hal Murray
> Since it is a string, maybe send something nicer? The formatting should be done in ntpq. Your version of "nice" conflicts with mine. As far as I'm concerned, you can fix ntpq so it has an option to do anything you want as long as the default doesn't change. -- PS: My suggesti

Re: ntpq peers formatting needs floating point for time slots

2017-02-01 Thread Hal Murray
>> The printout in ntpq still needs floating point for big numbers. > Not sure how that would look. Ugly, but less ugly than the current setup. In case I wasn't clear, instead of printing "-1234.5678", it should print "-1234.56". It's probably simplest to turn it into a string with 4 digits to

Re: ntpq peers formatting needs floating point for time slots

2017-02-01 Thread Gary E. Miller
Yo Hal! On Wed, 01 Feb 2017 15:11:42 -0800 Hal Murray 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 l28 377 0. -0.0050 0.0015 -clepsydra.labs. .GPS.

Re: ntpq peers formatting needs floating point for time slots

2017-02-01 Thread Gary E. Miller
Yo Hal! On Wed, 01 Feb 2017 15:11:42 -0800 Hal Murray wrote: > g...@rellim.com said: > > Eric did that. Also notice the LSB is always zero, which is > > clearly also wrong. > > I just pushed a fix. > > That stuff goes from ntpd to ntpq as text. It was 3 digits of > fraction. Now 6. Grea

Re: ntpq peers formatting needs floating point for time slots

2017-02-01 Thread Hal Murray
g...@rellim.com said: > Eric did that. Also notice the LSB is always zero, which is clearly also > wrong. I just pushed a fix. That stuff goes from ntpd to ntpq as text. It was 3 digits of fraction. Now 6. -- The printout in ntpq still needs floating point for big numbers. -- These

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

2017-02-01 Thread Gary E. Miller
Yo Hal! On Wed, 01 Feb 2017 14:06:18 -0800 Hal Murray wrote: > [I tried to submit an issue, but it was reject as spam.] Gitlab yesterday found spammers uing their submission system. Their cure was worse than the disease... > Somebody recently changed things to print out a 4th digit. That mad

ntpq peers formatting needs floating point for time slots.

2017-02-01 Thread Hal Murray
[I tried to submit an issue, but it was reject as spam.] Somebody recently changed things to print out a 4th digit. That made things worse. It was already broken if you had a negative number bigger than 1000 which isn't all that uncommon. ntpq -p remote refid st t when pol

Re: Reconstructing our issue list

2017-02-01 Thread Gary E. Miller
Yo Hal! On Wed, 01 Feb 2017 04:18:24 -0800 Hal Murray wrote: > It's reasonably easy to setup a cron job to make a copy of the data > in git. How many of us should do it? We already use github as a slave to gitlab, so I think out git is covered. > What do we have in the way of backup for our ot

Re: Reconstructing our issue list

2017-02-01 Thread Eric S. Raymond
Hal Murray : > It's reasonably easy to setup a cron job to make a copy of the data in git. > How many of us should do it? Git data and metadata are not the problem. Every pull of any of our reopositories replicates its entire state. What we risk losing is tracker data, and possibly the hooks

Re: Reconstructing our issue list

2017-02-01 Thread Hal Murray
It's reasonably easy to setup a cron job to make a copy of the data in git. How many of us should do it? Is there any way to grab a copy of the issues data? What do we have in the way of backup for our other stuff? How much is there that's not on gitlab? --- A while ago, I signed up fo

Re: Reconstructing our issue list

2017-02-01 Thread Hal Murray
* waf needs some tlc #212 ยท opened a month ago by Hal Murray updated 3 weeks ago waf check generates: ``` magic.pyc control.pyc version.pyc magic.pyo control.pyo version.pyo ``` waf build should have done all of that. ctx.add_group() is called after the ctx() calls to build c

Reconstructing our issue list

2017-02-01 Thread Eric S. Raymond
Gitlab has had an outage. They are working to recover, but it seems their backups were hosed and then someone made a finger error. It is possible that our issues and merge requests have been lost. Account of the incident here: https://docs.google.com/document/d/1GCK53YDcBWQveod9kfzW-VCxIABGiryG7