F20 Self Contained Change: Remove deprecated calls of using ntpdate in favor of ntpd

Adam Williamson awilliam at redhat.com
Wed Jul 17 20:48:04 UTC 2013


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.
> 
> 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.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net



More information about the devel mailing list