Public bug reported:

Currently the situation seems rather awkward and does not work how one
would want it (IMHO):

- has conflicts with systemd-timesyncd and openntp.service
  - ok to not start both at once
  - definition of conflicts is rather unclear, but due to condition checks in 
systemd-timesyncd this was working so far
- but it misses a conflicts with ntp.service

Systemd (systemd-timesyncd)
- used to not-start in presence of the others being installed
  - xenial had
  - the tail was from 
as part of systemd package
  - that is gone now (Bionic)
  - since other sevrices could be installed, but disabled this isn't perfect
    - but better than not disabling (that seems to be the current state)

  - installing ntp masks chrony (where is that done/how, does not seem to be 
postinst ?)
  - uninstall does not remove the mask so chrony is perma disabled after that

What do we actually want?
Well IMHO I think it is best described as "If pick the first from the following 
list IF INSTALLED AND RUNNING, if not fall through to next entry"
1. chrony
2. ntp
3. systemd-timesyncd

This might be a case of "perfection is the enemy of progress" but  lets 
evaluate the details and consider what should be done now and what maybe later 

** Affects: chrony (Ubuntu)
     Importance: Undecided
         Status: New

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  start/stop of conflicting time services not well coordinated

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to