Re: [chrony-users] DNS RR and chrony

2016-03-18 Thread Bryan Christianson
> On 18/03/2016, at 6:34 AM, Miroslav Lichvar wrote: > > > If you start chronyc with -c and write commands to the stdin, the > tracking command will still print the report in the CSV format. Oh - Thats cool thanks :) > >> Would it be possible to add an optional argument

Re: [chrony-users] DNS RR and chrony

2016-03-18 Thread Bryan Christianson
> On 18/03/2016, at 4:30 AM, Miroslav Lichvar wrote: > > > Also, chronyc now has a -c option to print reports in a CSV format, > all values in the same units. It should be much easier to parse if > anyone still needs to do that. > The -c output from chronyc looks really

Re: [chrony-users] DNS RR and chrony

2016-03-17 Thread Ben Kochie
On Thu, Mar 17, 2016 at 8:04 PM, Bryan Christianson wrote: > > > On 18/03/2016, at 6:34 AM, Miroslav Lichvar wrote: > > > > > > If you start chronyc with -c and write commands to the stdin, the > > tracking command will still print the report in the CSV

Re: [chrony-users] DNS RR and chrony

2016-03-17 Thread Miroslav Lichvar
On Fri, Mar 18, 2016 at 05:27:19AM +1300, Bryan Christianson wrote: > The -c output from chronyc looks really good and useful. > > My OSX program, ChronyControl, runs a persistent connection to chronyc and > sends it a ‘tracking’ command every (user configurable) few seconds. > Currently this

Re: [chrony-users] DNS RR and chrony

2016-03-17 Thread Ben Kochie
The CSV format looks great, I also tested the randomization which works well. The -v help output does't match the CSV, but that's a minor nit-pick. :) Thanks for looking into this. I'm still interested in writing a chrony client in Go or Python so I can create a fully integrated metrics

Re: [chrony-users] DNS RR and chrony

2016-03-17 Thread Miroslav Lichvar
On Thu, Feb 25, 2016 at 12:51:49PM +0100, Miroslav Lichvar wrote: > On Wed, Feb 24, 2016 at 04:18:36PM +0100, Ben Kochie wrote: > > The end result here is that getaddrinfo() always sorts the output of IPv4 > > results and chrony will pick the first N in that list. For example I have > > a DNS

Re: [chrony-users] DNS RR and chrony

2016-02-25 Thread Miroslav Lichvar
On Wed, Feb 24, 2016 at 04:18:36PM +0100, Ben Kochie wrote: > The end result here is that getaddrinfo() always sorts the output of IPv4 > results and chrony will pick the first N in that list. For example I have > a DNS record internally that has 8 servers, and I have chrony pick 4. > Every node

[chrony-users] DNS RR and chrony

2016-02-24 Thread Ben Kochie
When using pools in the config, chrony is subject to some implementation "problems" with libc's getaddrinfo() on many platforms. This breaks DNS round-robin as served by the DNS server. There is a long standing "bug" in several libc implementations due to strict adherence to RFC 3484 Rule #9.