systemd-timesyncd as my system timekeeper for several years now. I run a Debian derivative called raspbian for my Raspberry Pis. I'm mostly very pleased with the SNTP client that is
systemd-timesyncd, but would like to experiment with
chronyd for use in off-grid applications.
The following command may be used to list the configuration of
$ systemctl cat systemd-timesyncd
In buster, there was a section of code in this listing that provided
systemd-timesyncd with the ability to "excuse itself" if it found another timekeeping service (NTP daemon) installed:
# /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
At some point after the release of buster (concurrent w/ release of bullseye??), the above scheme was altered; the command
systemctl cat systemd-timesyncd no longer contains any references to restricting or inhibiting startup of
systemd-timesyncd if other timekeepers are found.
Does anyone recall the history of this change? More importantly, does
systemd-timesyncd still inhibit its startup if it finds another timekeeping daemon installed? Where/how is this done?