SYSTEMD-TI...D.SERVICE(8)

📦
version 261.3 · 15 versions
, in ubuntu stonking

💖 systemd-timesyncd.service(8) — network time sync, but make it group chat 💖

okay so welcome to the systemd-timesyncd.service(8) manual page, bestie. this is the one about keeping your clock cute and roughly on time. no cap, it’s literally clock business. 🕰️✨

✨ NAME ✨

systemd-timesyncd.service, systemd-timesyncd — Network Time Synchronization. that’s the name, and yes it’s giving “systemd but specifically for time vibes.” 💅

🦋 SYNOPSIS 🦋

systemd-timesyncd.service

/usr/lib/systemd/systemd-timesyncd

💅 DESCRIPTION 💅

systemd-timesyncd.service is a system service that may be used to synchronize the local system clock with a remote Network Time Protocol (NTP) server. it also saves the local time to disk every time the clock has been synchronized, and uses this to possibly advance the system realtime clock on subsequent reboots. why? to ensure it (roughly) monotonically advances even if the system lacks a battery-buffered RTC chip. 🕰️💖

the systemd-timesyncd.service service implements SNTP only. this minimalistic service will step the system clock for large offsets or slowly adjust it for smaller deltas. complex use cases that require full NTP support (and where SNTP is not sufficient) are not covered by systemd-timesyncd.service. so like, don’t ask it to do full-NTP main character work. 💀

the NTP servers contacted are determined from the global settings in timesyncd.conf(5), the per-link static settings in .network files, and the per-link dynamic settings received over DHCP. see systemd.network(5) for further details. 🛰️

timedatectl(1)'s set-ntp command may be used to enable and start, or disable and stop this service. love that for us. 🫶

timedatectl(1)'s timesync-status or show-timesync command can be used to show the current status of this service. status check, but make it clock. 👑

initialization of systemd-timesyncd.service delays the start of units that are ordered after time-set.target (see systemd.special(7) for details) until the local time has been updated from /var/lib/systemd/timesync/clock (see below) in order to make it roughly monotonic. it does not delay other units until synchronization with an accurate reference time sources has been reached. use systemd-time-wait-sync.service(8) to achieve that, which will delay start of units that are ordered after time-sync.target until synchronization to an accurate reference clock is reached. ⏳

systemd and systemd-timesyncd advance the system clock to the "epoch" (the lowest date above which the system clock time is assumed to be set correctly). see "System clock epoch" section in systemd(1) for details. systemd will set the clock when initializing, but /var/lib/systemd/timesync/clock might not yet be available at that point. systemd-timesyncd will advance the clock when it is started and notices that the system clock is before the modification time of /var/lib/systemd/timesync/clock. literally “bestie your clock is behind, let’s fix that.” 😭🔥

🗂️ FILES 🗂️

🌸 /var/lib/systemd/timesync/clock 🌸

the modification time ("mtime") of this file is updated on each successful NTP synchronization or after each SaveIntervalSec= time interval, as specified in timesyncd.conf(5). 🕰️

if present, the modification time of this file is used for the epoch by systemd(1) and systemd-timesyncd.service. iconic little file, honestly. 💖

Added in version 219.

🧚 /run/systemd/timesync/synchronized 🧚

a file that is touched on each successful synchronization to assist systemd-time-wait-sync.service(8) service and other applications in detecting synchronization to an accurate reference clock. yes, it gets a little touch. very demure. 🎀

Added in version 239.

👀 SEE ALSO 👀

okay bestie that’s the whole page 💖 signed off with systemd 261.3 vibes, from the systemd-timesyncd.service(8) manual page. go keep your clock roughly monotonic and your vibes immaculate ✨🫶

📦 where this page comes from