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

[Paul Wouters]

On Wed, 17 Jul 2013, Chris Murphy wrote:

> a. ntpd/ntpdate aren't installed by default with Fedora 19. I don't see the 
> feature proposing this be changed.

That's a bug then. It is needed for DNSSEC.

> b. A default installation of Fedora 18/19, has no means of updating the RTC 
> correctly if it's off by more than 15 minutes; and 60 minutes with newer 
> kernels. An RTC wrong by more than an hour, e.g. two months ago, if I have an 
> internet connection chrony sets the system clock to the correct date/time.

It won't be able to do so when DNSSEC is enabled.

> If I don't have an internet connection, I'm relegated to a system time based 
> on the wrong RTC, which seems grossly broken to me.

Yes, and using at least the last good known timestamp from shutdown
would be a plus.

> d. This long bug, 816752, suggests, as a solution, installing ntpdate in 
> order to set the RTC. So if ntpdate is being deprecated as part of the 
> proposed feature, why is installing and using ntpdate being suggested as a 
> fix for the lack of chrony-kernel RTC sync support?
> https://bugzilla.redhat.com/show_bug.cgi?id=816752#c75

What I learned today, you can read "ntpdate" as "ntpd -q -g -x"

> e. Why isn't this functionality being added to chrony, rather than bouncing 
> us back to ntpd?

Well, my f18 does not even have chrony installed. Did that change for
f19? I don't see it at https://fedoraproject.org/wiki/Releases/19/FeatureList

> The time situation on Fedora makes me think the left hand and right hand are 
> doing different things.

Well, we're discussing it now. So the ntpdate feature could just be
renamed to "deal with time and no RTC properly"

Paul