About Archive Tags RSS Feed



23 October 2019 10:00

Today I was looking over a system to see what it was doing, checking all the running processes, etc, and I spotted that it was running openntpd.

This post is a reminder to myself that systemd now contains an NTP-client, and I should go round and purge the ntpd/openntpd packages from my systems.

You can check on the date/time via:

$ timedatectl 
                      Local time: Wed 2019-10-23 09:17:08 EEST
                  Universal time: Wed 2019-10-23 06:17:08 UTC
                        RTC time: Wed 2019-10-23 06:17:08
                       Time zone: Europe/Helsinki (EEST, +0300)
       System clock synchronized: yes
systemd-timesyncd.service active: yes
                 RTC in local TZ: no

If the system is not setup to sync it can be enabled via:

$ sudo timedatectl set-ntp true

Finally logs can be checked as you would expect:

$ journalctl -u systemd-timesyncd.service



Comments on this entry

icon Paul Tötterman at 10:06 on 23 October 2019

IIRC systemd-timesynd is a SNTP client like openntpd and not a NTPv4 client like ntp or chrony.

icon Steve Kemp at 14:38 on 23 October 2019

Yes, I believe you're correct. Though in practice I've not noticed any difference so far.

(I had one test system setup like this when I first upgraded to the latest Stable Debian release. I've now updated all other hosts to match.)