Bug#805927: timesyncd does not automatically start after removing all NTP daemons

[Michael Biebl]

Hi Josh
Am 24.11.2015 um 06:53 schrieb Josh Triplett:
> Package: systemd
> Version: 228-2
> Severity: wishlist
> 
> /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
> disables systemd-timesyncd if /usr/sbin/ntpd (or another NTP daemon)
> exists.  However, nothing causes systemd-timesyncd to automatically
> start running after removing the last such daemon.  Would you consider
> adding such a mechanism?  (For instance, you could add a trigger in
> systemd that registers interest in the paths listed in
> disable-with-time-daemon.conf.)

We want to get rid of those hard-coded paths, not add them to more places.

> The reverse holds true as well: if you install such a daemon,
> systemd-timesyncd does not automatically stop.

The idea here is, that ntp, etc ship native service files, which have
Conflicts=systemd-timesyncd.service. So installing them should actually
stop timesyncd.

As for starting timesyncd automatically whenever ntp is removed: I have
to say, I don't particularly like the idea of installing dpkg triggers
for that. I mean, it wouldn't be too hard to manually start timesyncd.
Or on next reboot it would be started anyway.

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20151124/c5063163/attachment-0002.sig>