This bug was fixed in the package chrony - 3.2-2ubuntu2
---------------
chrony (3.2-2ubuntu2) bionic; urgency=medium
* d/control: use to nss instead of tomcrypt (in main) (LP: #1744072)
* d/chrony.conf: use ubuntu ntp pool and server (LP: #1744664)
* d/chrony.default, d/chrony.service: support /etc/default/chrony
DAEMON_OPTS in systemd environment (LP: #1746081)
* d/chrony.service: properly start after networking (LP: #1746458)
* d/usr.sbin.chronyd: allow to create /run/chrony on demand (LP: #1746444)
-- Christian Ehrhardt <[email protected]> Fri, 19 Jan
2018 09:45:38 +0100
** Changed in: chrony (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744072
Title:
MIR Chrony in 18.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ntp-charm/+bug/1744072/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
