I talked about this issue in #systemd on freenode and things work like I suspected from the docs. Just enabling chrony and having that Conflicts line is not enough to guarantee that chrony and not timesyncd is started on startup. That just XORs between the two.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779621 Title: chrony exits unexpectedly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1779621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
