On Mon, Feb 16, 2015 at 03:30:52PM +0000, Rob wrote: > Miroslav Lichvar <[email protected]> wrote: > > On Mon, Feb 16, 2015 at 02:00:30PM +0000, Rob wrote: > >> Is chronyc of 1.31 compatible with chronyd 2.0? > > > > Yes, old configuration should still work. But you can use > > "acquisitionport 123" as a workaround if you prefer stable version. > > Well I tried that before and it did not solve that issue.
Hm, you are right. I tried it again and it seems this works only with 1.30 and not 1.31. > What I mean is can I manage a mix of 1.31 and 2.0 servers from a single > system with one version of chronyc. Yes, that should be compatible. The cmdmon protocol was just extended (with one command - runtime makestep configuration) between 1.31 and 2.0. With 2.0 chronyc you can do everything 1.31 chronyc does, with 1.31 chronyc you can do everything except that one command. For 2.0, you will need to add "bindcmdaddress 0.0.0.0" to chrony.conf for as it binds to the loopback interface by default now. > It would be nice when chronyd could be contacted using ntpq with at > least the -p and the -c rv commands. Then the monitoring system does > not need to know what kind of ntp daemon is running on the servers. It would make the monitoring easier, but chronyd has different internal variables so it would have to be an emulation even if only the -p and -c rv commands were supported. >From the security point of view, I'd prefer to not have any support for the private/control modes of NTP. The chrony protocol runs on a separate port and the access can be tightly controlled, independently from NTP access. -- Miroslav Lichvar _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
