I wish systemd (timedatectl) would check if another NTP is running before taking control itself.
Same problem here:
Last login: Wed Feb 11 18:03:36 2026 from 192.168.1.102
root@server:~# apt show systemd-timesyncd chrony | grep -E '(^Package|time-daemon)'
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Package: systemd-timesyncd
Provides: time-daemon
Conflicts: systemd (<< 256.2-2~), time-daemon
Replaces: time-daemon
Package: chrony
Provides: time-daemon
Conflicts: time-daemon
Replaces: time-daemon
root@server:~#
However, I could have installed it too from source in the past, this OS has been installed and upgraded over the years, probably 20 years or so, without ever being formatted.
I could easily have messed up things, but I do not understand that during update change from SystemV (I think it’s called that) to Systemd they didn’t check.
I do not know what Debian started on this machine, but could be 6 or so, really don’t know.
Never needed to worry.
I find it silly they do not ask you about your timeserver OR the one you want to use. Should be a part of the package-select during initial install, or offer it again during dist-upgrades.
Ubuntu is even worse, they don’t even bother to inform you, they simply (re-)move to what they seem fit.