Some further looking at the systemd side, Bionic no longer carries the override conf (disable-with-time-daemon.conf) in favor of updating each client's systemd unit to use:
Conflicts=systemd-timesyncd.service Conflicts will ensure that the target service is stopped if the current unit is started. So, if ntp or chrony unit were to start, it would stop timesyncd. This is roughly equivalent, however, it does leave timesyncd unit enabled. This means that if something starts systemd-timesyncd.service, it would stop the ntp or chrony service. There may be additional work on each of the time packages to *disable* timesyncd unit when installed such that it won't start. This may not be possible to prevent users from starting timesyncd manually. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749722 Title: NTP: take into account systemd-timesyncd where present To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1749722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
