Seems like it's a systemd bug if anything then. I only got chrony to
work by disabling timesyncd but apparently you can make this work
without doing that.
The docs don't make it very clear that using conflicts will work
properly:
"""
Conflicts=
A space-separated list of unit names. Configures negative
requirement dependencies. If a unit has a Conflicts= setting on another
unit, starting the former will stop the latter and vice versa. Note that
this setting is independent of and orthogonal to the After= and Before=
ordering dependencies.
If a unit A that conflicts with a unit B is scheduled to be started at the
same time as B, the transaction will either fail (in case both are required
part of the transaction) or be modified to be fixed (in case one or both jobs
are not a required part of the transaction). In the latter case, the job that
is not the required will be removed, or in case both are not required, the unit
that conflicts will be started and the unit that is conflicted is stopped.
"""
It seems that depending on the boot order the chrony Conflicts line will
result in timesysncd or chrony but never both to be started. Maybe for
some reason my start order is different than the one you tested?
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
