Bug#883241: chrony: daemon doesn't automatically start

[Andres Salomon]

Sorry, I stopped using chrony some time ago and the laptop that was 
generating this bug was murdered by a cup of tea.


On Sat, Oct 5, 2019 at 02:43, Michael Biebl <biebl at debian.org> wrote:
> Seems like Conflicts= do not work reliably to ensure the
> systemd-timesyncd.service is not started during boot.
> 
> See also the upstream bug report
> <https://github.com/systemd/systemd/issues/7104>
> 
> We've re-added the Conditions to systemd-timesyncd.service.
> #
> /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
> [Unit]
> # don't run timesyncd if we have another NTP daemon installed
> ConditionFileIsExecutable=!/usr/sbin/ntpd
> ConditionFileIsExecutable=!/usr/sbin/openntpd
> ConditionFileIsExecutable=!/usr/sbin/chronyd
> ConditionFileIsExecutable=!/usr/sbin/VBoxService
> 
> 
> This should ensure systemd-timesyncd.service is not started if chrony 
> is
> installed.
> 
> Andres, can you still reproduce the problem?
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20191102/95eebf82/attachment.html>