On Wed, Jul 17, 2013 at 07:59:11AM -0600, Chris Murphy wrote: > > a. ntpd/ntpdate aren't installed by default with Fedora 19. I don't see the > feature proposing this be changed.
Also, there is already a replacement for ntpdate, it's in the sntp package. > 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. 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. It was fixed in kernel 3.10, which should be in f19 soon. > 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 > > 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 time situation on Fedora makes me think the left hand and right hand are > doing different things. -- Miroslav Lichvar -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
