Comment 2 for bug 1764357
Revision history for this message
| Christian Ehrhardt (paelzer) wrote Re: start/stop of conflicting time services not well coordinated | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
demo site
(Get the code!)
Status right now:
ok - 0. systemd-timesyncd
ok - 1. default install - install chrony => Chrony
fail - 1b. - remove chrony => none (ok after reboot)
ok - 2. default install - install ntp => NTP
fail - 2b. - remove ntp => none (ok after reboot)
ok - 3. default install - install openntp => openntp
fail - 3b. - remove openntp => none (ok after reboot)
ok - 4. default install - install ntp, install chrony => Chrony
fail - 4b. remove chrony => none (NTP masked by chrony install)
fail - 4c. remove NTP => systemd-timesyncd
fail - 5. default install - install chrony, install NTP => NTP (masked chrony on install)
ok - 5b. remove Chrony => NTP
fail - 5c. remove NTP => systemd-timesyncd
ok - 6. default install - install openntp => openntp
ok - 6b. install NTP => NTP
ok - 6c. install chrony => chrony
fail - 6d. remote NTP & Chrony => openntp (due to conflicts now nothing is her anymore)
fail - 6e. remove openntp => systemd-timesyncd
ok - 7. xenial with ntp - upgrade to B => NTP
ok - 8. xenial with ntp - upgrade to B, install chrony => Chrony
fail - 9. xenial with ntp - upgrade to B, remove NTP => systemd-timesyncd (ok after reboot)
ok - 10. xenial without ntp - upgrade to B => systemd-timesyncd