Miroslav Lichvar <[email protected]> wrote: > 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.
Ok I have compiled the new version and changed those config items and now it replies to NTP requests. Thanks. The PPS refclock has changed is refid from PPP0 to PPP1 with this version. I have added "refid PPS" now. Now I am going to monitor it a bit and see if it can be installed on the other PPS synced servers (instead of ntpd). I am still experimenting with the field from "tracking" to use instead of the var "offset" in ntpq. (I am graphing this value in nagios to watch the time inaccuracy, which should be within a few microseconds in my application) _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
