Re: possible bug: peerstats

Hal Murray : > > > Maybe. On the other hand, Classic mode wouldn't actually buy them much. The > > only scripts a typical leaf-node installation runs come right out of the NTP > > source tree themselves, and ours do the right thing. > > Would it be better if we changed

Re: possible bug: peerstats

> Maybe. On the other hand, Classic mode wouldn't actually buy them much. The > only scripts a typical leaf-node installation runs come right out of the NTP > source tree themselves, and ours do the right thing. Would it be better if we changed that to a run time decision rather than build

Re: possible bug: peerstats

Eric S. Raymond via devel writes: > Achim Gratz via devel : >> I'll have to change my data munging scripts to recognize these correctly >> so that the data goes where it's supposed to be. > > Yeah, sorry about that. We thought long and hard about this change, > and concluded it

Re: possible bug: peerstats

Achim Gratz via devel : > I'll have to change my data munging scripts to recognize these correctly > so that the data goes where it's supposed to be. Yeah, sorry about that. We thought long and hard about this change, and concluded it was necessary in order to server ntpd from

Re: possible bug: peerstats

Eric S. Raymond via devel writes: > The logging code shouldn't *know* what syntax was used to configure > the entry. Internally, the new syntax is converted to the equivalent > magic IP address by the configuration parser with this code: In fact it doesn't, I had already wondered why that would

Re: possible bug: peerstats

Achim Gratz via devel : > > I've updated to ntpsec-0.9.7+1104 ten days ago and just realized that > the peerstats logging has changed format: if I use the new refclock > syntax, then instead of the 127.127.. in the address > field, I now get the driver name like NMEA(0). I had

Re: possible bug: peerstats

Ian Bruene via devel writes: > This is a deliberate incompatibility with NTPclassic. Deliberate or not, I still consider it a bug that the same driver logs differently depending on how exactly it gets configured (refclock vs. server keyword), especially since ntpq would always show them

Re: possible bug: peerstats

On 08/19/2017 08:54 AM, Achim Gratz via devel wrote: I've updated to ntpsec-0.9.7+1104 ten days ago and just realized that the peerstats logging has changed format: if I use the new refclock syntax, then instead of the 127.127.. in the address field, I now get the driver name like NMEA(0). I

possible bug: peerstats

I've updated to ntpsec-0.9.7+1104 ten days ago and just realized that the peerstats logging has changed format: if I use the new refclock syntax, then instead of the 127.127.. in the address field, I now get the driver name like NMEA(0). I had written my scripts defensively enough to ignore