On Wed, Jul 17, 2013 at 01:48:04PM -0700, Adam Williamson wrote: > On Wed, 2013-07-17 at 13:44 -0700, Adam Williamson wrote: > > On Wed, 2013-07-17 at 16:09 +0200, Miroslav Lichvar wrote: > > > > > > e. Why isn't this functionality being added to chrony, rather than bouncing us back to ntpd? > > > > > > Which functionality exactly? Both ntpd and chronyd (in default > > > configuration) let the kernel sync the RTC. > > > > The ability to invoke chronyd in a way that mimics ntpdate. This thread > > has turned up that you can invoke *ntpd* in this way: ntpd -q -g -x. But > > no-one has yet provided an equivalent invocation for chronyd, and I > > could not figure one out from the manpage. chronyd doesn't have an "ntpdate" mode. I think that could be a useful feature and I'll see if it can be added. > > Aside from anything else, anaconda requires something like this to be > > available in order to check whether an NTP server is valid and > > available: a simple, one-off command which will 'return true' in some > > obvious way if the specified server exists and responds correctly, and > > 'return false' if it doesn't. For now it is using ntpdate; I suppose we > > could switch it to ntpd, but it would make an awful lot more sense if > > chronyd could do this. > > In fact, now I look at it, ntpd as it stands cannot replace ntpdate for > anaconda's purposes, because anaconda calls ntpdate with the -q option, > which means "query only, do not set the clock" - obviously, this is > appropriate when we just want to test the functionality of an NTP > server. ntpd does not have an equivalent option. The sntp tool can be used instead of ntpdate to test if an NTP server is responding. -- Miroslav Lichvar -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
