Domain 4Running SystemsCORE

Time Services

Guide to managing RHEL time services, time zones, hardware vs. system clocks, and Chrony NTP synchronization.

Domain: Operate running systems•Updated: 2026-08-30
#Time Services#NTP#Chrony#Timedatectl#RHCSA#RHEL

Time Services

Theory Questions

1. Identify the initial source of system time at boot.

  • Command(s):
dmesg | grep -i rtc
  • Why: At system boot, the Linux kernel initializes the software system clock from the hardware Real-Time Clock (RTC/CMOS chip) on the motherboard.
  • Gotchas: Expecting system time to automatically sync with remote NTP servers before network interfaces initialization occurs.
  • Verify:
timedatectl status

2. Evaluate statements about local time, DST, and hardware time.

  • Command(s):
timedatectl status
  • Statements Evaluation:

  • True: Hardware clock (RTC) should ideally be configured to Universal Time Coordinated (UTC) to avoid Daylight Saving Time (DST) calculation errors.

  • True: Local time is calculated dynamically by applying system time zone rules and DST offsets to UTC.

  • False: Configuring the hardware clock to local time (RTC in local TZ: yes) is recommended for RHEL servers. (Correction: Storing local time in RTC can cause offset glitches during DST transitions.)

  • Why: Setting RTC to UTC prevents time shifts during seasonal DST transitions across system reboots.

  • Gotchas: Setting RTC in local TZ: yes via timedatectl set-local-rtc 1, which triggers system warnings.

  • Verify:

timedatectl | grep "RTC in local TZ"

  • Command(s):
timedatectl set-timezone America/New_York
  • Why: timedatectl set-timezone updates the /etc/localtime symbolic link to point to the designated binary zoneinfo file in /usr/share/zoneinfo/.
  • Gotchas: Manually copying file binaries into /etc/localtime instead of creating atomic symlinks via timedatectl.
  • Verify:
timedatectl | grep "Time zone"

4. Choose the most accurate clock type for an isolated server.

  • Command(s):
# Enable chrony local reference mode in isolated environments:
echo "local stratum 10" >> /etc/chrony.conf
systemctl restart chronyd
  • Why: For isolated servers lacking external network connectivity, high-precision hardware RTCs or internal local reference clocks (PTP/Atomic hardware) serve as the primary stratum source.
  • Gotchas: Attempting to query public NTP pools from air-gapped systems without an internal fallback clock defined.
  • Verify:
chronyc tracking

5. Identify the configuration file containing the default NTP server list.

  • Path / Command:
/etc/chrony.conf
  • Why: /etc/chrony.conf is the primary configuration file for chronyd, containing pool and server directives alongside drift file directives.
  • Gotchas: Searching for /etc/ntp.conf (NTPd is deprecated in modern RHEL distributions in favor of Chrony).
  • Verify:
grep -E "^(server|pool)" /etc/chrony.conf

6. Set the current system time to a specific time.

  • Command(s):
timedatectl set-ntp false
timedatectl set-time "2026-08-30 14:30:00"
  • Why: Manual system time overrides require disabling active network time synchronization (set-ntp false) before issuing set-time.
  • Gotchas: Executing timedatectl set-time while NTP synchronization is active results in Failed to set time: Automatic time sync is enabled error.
  • Verify:
date

7. Translate epoch time into human-readable time.

  • Command(s):
date -d @1788000000
  • Why: The -d @<timestamp> flag instructs date to parse Unix epoch seconds (seconds elapsed since 1970-01-01 00:00:00 UTC) into formatted human-readable output.
  • Gotchas: Omitting the required @ prefix before the epoch integer string.
  • Verify:
date -d @$(date +%s)

8. Set the system time to match the current hardware clock.

  • Command(s):
hwclock --hctosys
  • Why: --hctosys reads the hardware Real-Time Clock (RTC) value and overwrites the active Linux kernel system clock.
  • Gotchas: Inverting flags to --systohc, which writes system time to hardware time instead.
  • Verify:
timedatectl

9. Display local time, hardware time, and time zone information.

  • Command(s):
timedatectl status
  • Why: timedatectl status displays Local time, Universal time (UTC), RTC time, active Time zone, and NTP synchronization flags in a single output block.
  • Gotchas: Using standard date, which only displays software system time and local zone offset.
  • Verify: Inspect output of timedatectl status.

10. Verify that a chrony time client has successfully synchronized.

  • Command(s):
chronyc tracking
chronyc sources -v
  • Why: chronyc tracking displays reference ID, stratum level, and time offset, while chronyc sources displays peer status (an asterisk * indicates the current synchronized source).
  • Gotchas: Running systemctl status chronyd, which only confirms daemon process execution, not NTP network synchronization lock.
  • Verify:
chronyc sources | grep "\*"

11. Set the system time to a specific time (e.g., 4:24 p.m.).

  • Command(s):
timedatectl set-ntp false
timedatectl set-time "16:24:00"
  • Why: timedatectl set-time accepts 24-hour timestamp strings (HH:MM:SS) once NTP active sync is disabled.
  • Gotchas: Entering 12-hour values without explicit 24-hour conversion or failing to turn off NTP service.
  • Verify:
date +%T

12. Set hardware time to the current system time.

  • Command(s):
hwclock --systohc
  • Why: --systohc (System to Hardware Clock) updates the motherboard Real-Time Clock (RTC) chip using current software system time values.
  • Gotchas: Using --hctosys, which overwrites software system time with hardware RTC values.
  • Verify:
hwclock --show

13. Display epoch time as human-readable time.

  • Command(s):
date -d @1756512000
  • Why: Prepending @ to the target numerical value allows date -d to evaluate Unix epoch time stamps into local zone strings.
  • Gotchas: Passing raw epoch numbers directly without the leading @ parameter.
  • Verify:
date -d @0

(Returns Thu Jan 1 00:00:00 UTC 1970 or local equivalent)


14. Synchronize the system clock with hardware time.

  • Command(s):
hwclock --hctosys
  • Why: Reads current CMOS/RTC values and updates system kernel time.
  • Gotchas: Confusing --hctosys with --systohc.
  • Verify:
timedatectl

15. Identify the NTP time management service on RHEL 9.

  • Command(s):
systemctl status chronyd
  • Why: chronyd is the default NTP synchronization daemon for modern Enterprise Linux releases.
  • Gotchas: Attempting to query or start the legacy ntpd service.
  • Verify:
systemctl is-active chronyd

16. Enable NTP time synchronization on your server.

  • Command(s):
timedatectl set-ntp true
systemctl enable --now chronyd
  • Why: timedatectl set-ntp true activates systemd time synchronization hooks, delegating active clock drift adjustments to chronyd.
  • Gotchas: Executing set-ntp true while chronyd service is masked or disabled.
  • Verify:
timedatectl status | grep "NTP service"

17. Identify the configuration file listing NTP servers.

  • Path / Command:
/etc/chrony.conf
  • Why: Main configuration file containing network NTP server endpoints, pool settings, allowed subnet client access controls, and drift file locations.
  • Gotchas: Editing /etc/ntp.conf (which does not exist by default on RHEL 9/10).
  • Verify:
grep "^pool\|^server" /etc/chrony.conf

18. List available time zones.

  • Command(s):
timedatectl list-timezones
  • Why: Queries system zoneinfo database to return all valid IANA time zone identifier strings.
  • Gotchas: Typing manual region strings into set-timezone without verifying exact string matches via list-timezones.
  • Verify:
timedatectl list-timezones | grep -i "america/new_york"

19. Set the current time zone.

  • Command(s):
timedatectl set-timezone America/New_York
  • Why: Directs system clock offset calculations to standard regional IANA zone definitions.
  • Gotchas: Using non-standard time zone abbreviations (e.g., EST or EDT) instead of standard Area/Location entries.
  • Verify:
timedatectl | grep "Time zone"

20. Use chrony to set system time.

  • Command(s):
chronyc makestep
  • Why: Forces chronyd to immediately step (jump) system time to offset values instead of gradually slewing clock drift over extended execution windows.
  • Gotchas: Waiting for natural chrony slewing when an immediate offset jump is required during system configuration.
  • Verify:
chronyc tracking

Lab Tasks

Task 1: Time Services Practice

  • Compare the current hardware time to the system time. If there is a difference, synchronize them.
  • Command(s):
timedatectl status
hwclock --hctosys
timedatectl status
  • Why:

  • timedatectl status: Evaluates time variations between System time (Local time) and RTC time (Hardware time).

  • hwclock --hctosys: Synchronizes the kernel software clock to match the hardware RTC value.

  • Gotchas: Executing --systohc instead of --hctosys, which would overwrite hardware RTC time with inaccurate system clock values.

  • Verify:

timedatectl status

(Inspect Local time and RTC time lines to confirm clock alignment)


Task task 2: Time Zone Configuration Practice

  • Set the time zone to correspond to Boston (USA East Coast).
  • Command(s):
timedatectl set-timezone America/New_York
  • Why: Sets the system time zone to Eastern Standard Time (EST/EDT) matching Boston, Massachusetts (USA East Coast).
  • Gotchas: Searching for America/Boston in zoneinfo lists; Boston uses the America/New_York IANA time zone reference.
  • Verify:
timedatectl | grep "Time zone"

(Output should display Time zone: America/New_York (EDT, -0400) or (EST, -0500))