[chrony-dev] Chrony is great, but...

[ Thread Index | Date Index | More chrony.tuxfamily.org/chrony-dev Archives ]


Having just upgraded from Fedora 16 to Fedora 19, the NTP client
changed from ntpd to chronyd.  chronyd seems to be in improvement in
many ways, but ... you can't access it with ntpq and ntptrace.  And I
use some (simple) tools to monitor NTP using the ntp* programs.  So I
replaced chronyd with ntpd.  It's a step backward, but it works.

This wouldn't be interesting if ntpq communicated with ntpd using a
non-standard protocol (which appears to be how chronyc communicates
with chronyd).  But the NTP control protocol is standardized in RFC
1305 appendix B.  I believe that you would make chrony a lot more
useful in the real world if it was enhanced to support at least the
monitoring commands of the NTP control protocol.

Dale

-- 
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.


Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/