Linux course index · Linux Advanced category · Lesson 7 of 9
AI disclosure — AI-generated content, posted as is. AI can make mistakes. This lesson draws on the linked Open Education posts and adds original explanations or lab examples where useful. The newly written explanations and examples may be freely reused. Linked source material retains its own terms.
Learning goal
Distinguish clock display from synchronization and show whether chrony selected a source.
Concepts and setup
Clock agreement matters for log correlation, certificate validity, and scheduling. A timezone changes the display of wall time. It does not fix clock drift or change the synchronization reference. The archive uses older ntpd and ntpq commands. This lesson translates those diagnostics to chrony where installed. Some systems use a different client, such as systemd-timesyncd. Avoid having multiple daemons try to adjust the same clock.
Inspect the clock and selected source
date -u '+%F %T UTC'
timedatectl status
chronyc -n sources -v
chronyc tracking
Possible output
2026-11-16 19:30:15 UTC
...
System clock synchronized: yes
...
^* 192.0.2.40 ... +21us[+15us] +/- 14ms
Stratum : 3
System time : 0.000015000 seconds fast of NTP time
Leap status : Normal
The address is illustrative. A star marks the selected source. Compare the system clock and chrony results rather than inferring synchronization just because a service runs.
Read time-service evidence
systemctl list-unit-files 'chrony*.service'
# Choose your installed name. This one is common on Red Hat-family systems.
journalctl -b -u chronyd.service -n 20 --no-pager
chronyc -n activity
Possible output
chronyd.service enabled ...
... Selected source ...
4 sources online
0 sources offline
...
0 sources with unknown address
On Ubuntu the unit may be chrony.service. Use approved time sources and confirm the network policy. Client troubleshooting does not call for opening an inbound time service or forcing a time step.
Questions only
Quick-check questions
- What does ^* indicate in chronyc sources?
- Does changing the display timezone alter NTP synchronization?
Assessment questions
- Tracking reports an unsynchronized state. What evidence should you gather?
- Why might the clock in a VM drift even though its host is synchronized?
- Name two applications where you would notice a time error.
Questions and answers
Quick-check answers
- What does ^* indicate in chronyc sources?
Answer — ^ means an NTP server source and * marks the selected one. - Does changing the display timezone alter NTP synchronization?
Answer — No. It changes how local time is displayed.
Assessment answer key
- Tracking reports an unsynchronized state. What evidence should you gather?
Answer — Check the daemon status, approved sources, source selection and reachability, route or DNS if relevant, and journal. - Why might the clock in a VM drift even though its host is synchronized?
Answer — The guest has its own clock behavior and scheduling. It can require its own synchronization policy or managed guest integration. - Name two applications where you would notice a time error.
Answer — Examples include TLS certificate validation and log correlation across machines.
Source articles on this site
- NTP related commands/Linux #DevOps #RHCSA
- NTP related commands/Linux
- Basic Commands for Networking in Linux
Technical references
Continue the course
Previous lesson 06 — DHCP Leases and a Kea Lab. Next lesson 08 — Apache Virtual Hosts and HTTPS.
Linux course index · Linux Advanced category · Lesson 7 of 9
