Hello, yes, /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time- daemon.conf has the same contents as you pasted and systemd properly reports condition failed for systemd-timesyncd.
I cannot really reproduce this behaviour. Something was listening upon boot and that is odd. But anyway that misses the point. Regardless of what caused ntp to fail, in my opinion: a) systemd should make attempts to restart it - it didn't b) /etc/init.d/ntp start shouldn't silently fail (that was the behaviour) However, I will probably revert to systemd-timesyncd and abandon using ntpd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703381 Title: ntpd does not restart after failing to start upon boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1703381/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
