On Tue, 5 Dec 2017 00:55:43 -0800 Andres Salomon <dilin...@queued.net> wrote:
> Alright, some progress...
>
> Vincent asked me privately to try switching to sysvinit. When I did
> that, chronyd started successfully on boot. So that narrows it down
> to some kind of systemd interaction problem.
>
> I messed around with the chronyd.service file, and commenting out the
> Conflicts line resulted in chronyd starting at boot with systemd:
And specifically, it's conflicting with timesyncd.
"Conflicts=openntpd.service" allows chronyd to start up just fine.
dilinger@e7450:~$ sudo systemctl status systemd-timesyncd
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled;
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
└─disable-with-time-daemon.conf
Active: inactive (dead)
Condition: start condition failed at Tue 2017-12-05 00:59:47 PST; 16min ago
└─ ConditionFileIsExecutable=!/usr/sbin/chronyd was not met
Docs: man:systemd-timesyncd.service(8)
Openntpd in Debian Stable has this in its openntpd.service file:
Conflicts=systemd-timesyncd.service
Ntp in Debian Stable doesn't appear to ship with a .service file..
pgp6UJLO5LVi6.pgp
Description: OpenPGP digital signature
