[pkg-ntp-maintainers] Bug#873057: ntp: ntpd not started at boot

[Michael Biebl]

On Thu, 24 Aug 2017 09:38:55 +0300 Esa Peuha <esa.peuha at gmail.com> wrote:
> Source: ntp
> Version: 1:4.2.8p10+dfsg-5
> 
> I have an installation of Debian testing with ntp installed on it. With
> ntp version 1:4.2.8p10+dfsg-3 and earlier, ntpd was started during boot,
> but with 1:4.2.8p10+dfsg-4 and -5, ntpd isn't started (which BTW is far
> from obvious; I became aware of the issue only after I noticed that the
> machine's clock had drifted about a minute from the correct time). If I
> copy /lib/systemd/system/ntp.service to /etc/systemd/system/ntp.service
> and comment out the line "Conflicts=systemd-timesyncd.service" then ntpd
> is started again, so I suggest that you remove that line. It shouldn't
> be necessary for ntp to conflict with timesyncd anyway, because the file
> /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
> checks if /usr/sbin/ntpd exists, and doesn't start timesyncd if it does.
> 
> 

/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
was a stop-gap solution for stretch, as at the time, ntp didn't ship a
native systemd unit.
It's not a good solution though, as it only tests for the existence of
the ntp binary, not if the actual service is actually active and running.

The correct fix is having Conflicts=systemd-timesyncd.service in
ntp.service.
It's good to see that this is now the case.
Please don't drop that again!

Instead we should remove
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
from the systemd package.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-ntp-maintainers/attachments/20170825/1a041966/attachment.sig>