/usr/lib/systemd/system/ntpd.service Wants=ntp-wait.service there is no "ntp-wait.service" in F18 so what about read /var/log/messages after boot?
The service is in the ntp-perl subpackage. What messages do you see?
a logical one for a Wants=non-existing-unit Feb 1 13:22:33 testserver systemd[1]: Cannot add dependency job for unit ntp-wait.service, ignoring: Unit ntp-wait.service failed to load: No such file or directory. See system logs and 'systemctl status ntp-wait.service' for details.
Before installing ntp-perl, I was getting this in /var/log/messages: Mar 4 23:54:59 athena systemd[1]: Cannot add dependency job for unit ntp-wait.s ervice, ignoring: Unit ntp-wait.service failed to load: No such file or director y. See system logs and 'systemctl status ntp-wait.service' for details. Mar 4 23:54:59 athena systemd[1]: Found ordering cycle on basic.target/start Mar 4 23:54:59 athena systemd[1]: Walked on cycle path to sockets.target/start Mar 4 23:54:59 athena systemd[1]: Walked on cycle path to dbus.socket/start Mar 4 23:54:59 athena systemd[1]: Walked on cycle path to sysinit.target/start Mar 4 23:54:59 athena systemd[1]: Walked on cycle path to auditd.service/start Mar 4 23:54:59 athena systemd[1]: Walked on cycle path to readahead-sort.servic e/start Mar 4 23:54:59 athena systemd[1]: Walked on cycle path to basic.target/start Mar 4 23:54:59 athena systemd[1]: Breaking ordering cycle by deleting job dbus. socket/start systemd deciding that dbus is the service not to start to break the cycle makes loads of other things fail. I don't understand why, but installing ntp-perl resolved *both* problems. I had no cycle messages and a normal boot after that.
there is no need to install ANYTHING "Wants=ntp-wait.service" is simply bogus and not needed and i am tired to fix the systemd-unit on each and every install
This comment was flagged a spam, view the edit history to see the original text if required.
ntp-4.2.6p5-11.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/ntp-4.2.6p5-11.fc19
Package ntp-4.2.6p5-11.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing ntp-4.2.6p5-11.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-4660/ntp-4.2.6p5-11.fc19 then log in and leave karma (feedback).
if i report abug for F18 it is NOT HELPFUL to get notified about F19/Rawhide-Updates while the problem on the reported version still exists
it's pretty much normal that the reporter is the first person who is willing to test and he is only willing to test or even only able to test for the release he has reported for, if not we would not need to select the release in the bugreport that is what updates-testing and scratch-builds are for notify me that a test-version exists for a distribution release which does not run on my machines and for which i had not reported the bug at least without having a F18 build within two days after the F19 one is a spit in the reporters face
ntp-4.2.6p5-11.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.