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.
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.