Re: F20 Self Contained Change: Remove deprecated calls of using ntpdate in favor of ntpd
Which gets me wondering if that is the best way to test for remote ntp connectivity.
So, I'm curious now, if there is no remote NTP server listening, will the anaconda server reject you from using that as a NTP server?
Mike
------------------------------
Message: 12 Date: Wed, 17 Jul 2013 13:48:04 -0700 From: Adam Williamson awilliam@redhat.com To: Development discussions related to Fedora devel@lists.fedoraproject.org Subject: Re: F20 Self Contained Change: Remove deprecated calls of using ntpdate in favor of ntpd Message-ID: 1374094084.1594.8.camel@adam Content-Type: text/plain; charset="UTF-8"
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
On Wed, 2013-07-17 at 15:10 -0600, Mike wrote:
Which gets me wondering if that is the best way to test for remote ntp connectivity.
So, I'm curious now, if there is no remote NTP server listening, will the anaconda server reject you from using that as a NTP server?
It lists the server addresses you enter or that are pre-filled with green and red 'traffic lights', red for 'this server appears to be broken/invalid', green for 'this server appears to be working'.
From: mikedawg@gmail.com To: devel@lists.fedoraproject.org Date: 07/17/2013 17:11 Subject: Re: F20 Self Contained Change: Remove deprecated calls of using ntpdate in favor of ntpd Sent by: devel-bounces@lists.fedoraproject.org
Which gets me wondering if that is the best way to test for remote ntp connectivity.
I think you want to work with:
chronyc tracking
Also, this might be useful too:
chronyc waitsync
-- John Florian
-
Adam Williamson -
John.Florian＠dart.biz -
Mike