Signal9Signal9 — home
online
back to labs

chrony: Point an NTP Client at Its Time Source

EasyRHCSA Prep10-20 min
The brief

This host runs chrony but has no time source configured, so its clock drifts. Configure it as an NTP client. Your assignment is in /root/case/assignment.env (NTP_SERVER, CHRONY_CONF).

Edit /etc/chrony/chrony.conf so chrony:

1. Uses NTP_SERVER as a time source, with the option that makes the first sync take seconds instead of minutes — a fast burst of requests at startup rather than one probe every few minutes.

2. Records the estimated clock drift to a driftfile, so the clock is accurate immediately after a reboot instead of re-learning the drift rate every time.

Grading reads /etc/chrony/chrony.conf. On a live host you'd then systemctl restart chronyd and verify with chronyc sources. See /root/case/brief.txt.

What you'll do
  • Read the per-session NTP server assignment
  • Add the server as a chrony time source
  • Enable iburst for fast initial synchronization
  • Configure a driftfile so drift persists across reboots

Hands-on lab: you work on a real Linux box in your browser, graded on the machine's actual state.