How To Set Date and Time on AlmaLinux 10

In this tutorial, we will show you how to set date and time on AlmaLinux 10. Proper date and time configuration forms the backbone of any reliable Linux system. AlmaLinux 10, as an enterprise-grade distribution, requires precise temporal settings for optimal performance, security, and operational efficiency. Whether you’re managing a single server or orchestrating an entire infrastructure, understanding how to configure system time correctly can prevent costly downtime and ensure seamless operations.

This comprehensive guide covers every aspect of date and time management on AlmaLinux 10. From basic GUI adjustments to advanced command-line configurations, you’ll master the tools and techniques necessary for maintaining accurate system time across your environment.

Why Accurate Date and Time Matter in AlmaLinux

System timing affects virtually every aspect of modern computing infrastructure. Inaccurate timestamps can compromise log file analysis, making troubleshooting nearly impossible when critical issues arise. Security protocols depend heavily on synchronized time for certificate validation and authentication processes.

Database operations require precise timing for transaction ordering and data integrity. Distributed systems coordination becomes chaotic without synchronized clocks across all nodes. Compliance requirements often mandate accurate timestamp records for audit trails and regulatory reporting.

Network protocols like Kerberos have strict time tolerance requirements, typically allowing only a few minutes of clock drift before authentication fails completely. Backup systems, monitoring tools, and automated scripts all rely on accurate system time to function properly.

Prerequisites and System Requirements

Before proceeding with time configuration, ensure your AlmaLinux 10 system meets basic requirements. You’ll need administrative privileges through either root access or sudo capabilities. Network connectivity is essential for NTP synchronization with external time servers.

Basic terminal familiarity will help you navigate command-line procedures effectively. If using GUI methods, ensure the GNOME desktop environment is installed and accessible. Most AlmaLinux installations include these components by default.

Understanding AlmaLinux Time Management System

AlmaLinux 10 utilizes a sophisticated time management architecture centered around systemd’s timedatectl utility. The system maintains time through several interconnected components working in harmony.

The /etc/localtime file serves as a symbolic link pointing to timezone data stored in /usr/share/zoneinfo. This structure allows the system to reference comprehensive timezone information while maintaining a simple configuration interface.

System time operates independently from the hardware clock (RTC), though both can be synchronized. UTC serves as the internal time standard, with local timezone adjustments applied for display purposes. The timedatectl command manages all these components through a unified interface.

Chrony has replaced traditional NTP as the default time synchronization daemon in AlmaLinux 10. This modern implementation provides better accuracy and handles network irregularities more gracefully than older alternatives.

Checking Current Date, Time, and Timezone Settings

Before making any modifications, examine your current time configuration. The timedatectl command without arguments displays comprehensive system time information:

timedatectl

This output reveals local time, universal time, RTC time, timezone, and synchronization status. Pay attention to the “System clock synchronized” field, which indicates whether NTP is functioning properly.

Verify the timezone symbolic link directly:

ls -l /etc/localtime

This command shows the actual timezone file being referenced, providing confirmation of your current timezone setting.

Alternative time checking methods include the traditional date command for quick time display and hwclock for hardware clock information. These commands provide additional perspectives on your system’s temporal state.

Setting Date and Time via GNOME GUI

AlmaLinux 10’s GNOME interface provides an intuitive approach to time management. Access the configuration through the Activities menu by searching for “time” or “date”.

Navigate to Settings > Date & Time to open the configuration panel. The interface requires administrative authentication before allowing modifications. Click the unlock button and enter your password when prompted.

The automatic time setting toggle controls whether your system synchronizes with network time servers. Enable this option for most scenarios unless specific requirements demand manual control. When automatic time is enabled, the system queries reliable time servers to maintain accuracy.

For manual configuration, disable automatic time and date settings. This unlocks the manual adjustment controls, allowing you to specify exact date and time values. Click on the displayed date or time to access modification dialogs.

Timezone configuration uses an interactive map interface or city search functionality. Select your geographic region or search for a major city in your timezone. The system automatically applies appropriate daylight saving time rules based on your selection.

Save changes by clicking the apply button or simply closing the settings window. The system immediately implements new time settings across all running processes and services.

Command-Line Date and Time Configuration

Command-line time management offers greater precision and scriptability than GUI methods. The timedatectl utility serves as the primary tool for time configuration tasks.

Using timedatectl for Basic Time Management

Setting system time manually requires disabling automatic synchronization first:

sudo timedatectl set-ntp off

Once synchronization is disabled, set specific date and time values:

sudo timedatectl set-time "2025-06-01 14:30:00"

The time format follows ISO 8601 standards, accepting various input formats including “YYYY-MM-DD HH:MM:SS”. Partial specifications are also valid – setting only date or only time while preserving the other component.

Managing Time Synchronization

Network time synchronization provides the most reliable method for maintaining accurate system time. Enable NTP synchronization with:

sudo timedatectl set-ntp on

Verify synchronization status by running timedatectl without arguments. The “System clock synchronized” field should indicate “yes” after successful NTP configuration.

When synchronization is active, manual time changes are overridden by network time servers. This prevents accidental time drift while ensuring consistency across your infrastructure.

Comprehensive Timezone Management

Timezone configuration affects how the system displays time to users and applications while maintaining UTC internally. Proper timezone selection ensures accurate local time display and correct daylight saving time transitions.

Listing and Selecting Timezones

Display all available timezones with:

timedatectl list-timezones

This command produces an extensive list organized by geographic regions. Use grep to filter results for specific areas:

timedatectl list-timezones | grep America

Timezone names follow the format “Continent/City” or “Region/Location”, providing clear geographic references for selection.

Changing Timezone Settings

Set your desired timezone using the timedatectl command:

sudo timedatectl set-timezone America/New_York

Replace “America/New_York” with your appropriate timezone identifier. The system immediately applies the new timezone setting without requiring a restart.

Verify the change by running timedatectl again to confirm the new timezone appears in the output.

Advanced Timezone Configuration

Hardware clock timezone settings affect dual-boot systems where multiple operating systems share the same hardware. Configure RTC to use local time when required:

sudo timedatectl set-local-rtc true

This setting is typically necessary only when sharing hardware with Windows systems that expect local time in the hardware clock.

Network Time Protocol (NTP) Configuration with Chrony

Chrony provides superior time synchronization compared to traditional NTP implementations. Its advanced algorithms handle network latency and interruptions more effectively while maintaining higher accuracy.

Installing and Configuring Chrony

Install Chrony if not already present:

sudo dnf install chrony

The main configuration file resides at /etc/chrony.conf. This file defines NTP servers, access controls, and synchronization parameters.

Edit the configuration file to specify reliable time servers:

sudo nano /etc/chrony.conf

Add or modify server entries to use geographically appropriate NTP pools:

pool 2.almalinux.pool.ntp.org iburst

The iburst option accelerates initial synchronization by sending multiple requests rapidly.

Advanced Chrony Configuration

Configure your system as a local NTP server for other network devices by adding access controls:

allow 192.168.1.0/24

This example permits access from the specified subnet range. Adjust the network address to match your infrastructure requirements.

Firewall configuration may be necessary to allow NTP traffic on UDP port 123. Configure firewalld to permit NTP communications:

sudo firewall-cmd --permanent --add-service=ntp
sudo firewall-cmd --reload

Monitor Chrony synchronization status using chronyc commands:

chronyc sources
chronyc tracking

These commands provide detailed information about time source quality and synchronization accuracy.

Troubleshooting Common Date and Time Issues

Time-related problems can manifest in various ways, from obvious clock drift to subtle synchronization failures affecting specific services.

Timezone synchronization problems often result from incorrect timezone selection or missing timezone data. Verify your timezone choice matches your geographic location and DST requirements.

Hardware clock drift occurs when the RTC loses accuracy over time. Modern systems typically maintain reasonable accuracy, but older hardware may require more frequent synchronization.

NTP connectivity issues prevent automatic time synchronization. Check network connectivity to time servers and verify firewall settings permit NTP traffic. DNS resolution problems can also prevent NTP from reaching configured servers.

Permission errors during configuration typically indicate insufficient administrative privileges. Ensure you’re using sudo or root access for system time modifications.

Dual-boot time conflicts arise when different operating systems disagree about hardware clock timezone settings. Configure all systems to use UTC internally to avoid these conflicts.

Best Practices and Security Considerations

Production environments require careful attention to time synchronization reliability and security implications. Select geographically close NTP servers with good reputation and availability records.

Implement redundant time sources by configuring multiple NTP servers. This prevents single points of failure and improves synchronization accuracy through comparison algorithms.

Monitor time synchronization status regularly through automated checks. Configure alerting when synchronization fails or drift exceeds acceptable thresholds.

Document time configuration changes as part of your change management processes. This documentation proves valuable during troubleshooting and audit activities.

Security considerations include restricting NTP access to trusted networks and monitoring for time-based attacks. Some security protocols become vulnerable when system time is manipulated maliciously.

Backup time configuration files before making changes. Store copies of /etc/chrony.conf and timezone settings to enable quick recovery if problems arise.

Advanced Scenarios and Use Cases

Multi-server environments benefit from hierarchical time distribution architectures. Configure primary servers to synchronize with external sources while secondary servers synchronize internally.

Container and virtualization platforms require special consideration for time synchronization. Virtual machines typically inherit time from their hypervisors, but containers may need explicit configuration.

Database servers often have specific timing requirements for transaction ordering and replication. Ensure database documentation includes appropriate time synchronization recommendations.

Web applications serving global audiences must handle timezone conversions correctly. Server timezone configuration affects log timestamps and may influence application behavior.

Scheduled tasks and cron jobs depend on accurate system time for proper execution. Document timezone dependencies when creating scheduled tasks that must run at specific local times.

Alternative Methods and Tools

While timedatectl provides the recommended interface for time management, alternative tools remain available for specific scenarios.

The traditional date command offers quick time display and basic setting capabilities:

date
sudo date -s "2025-06-01 14:30:00"

Hardware clock management uses the hwclock command:

hwclock --show
sudo hwclock --systohc

Third-party tools and GUI alternatives exist for specialized environments. Some administrators prefer traditional NTP client implementations for compatibility with existing monitoring systems.

Congratulations! You have successfully set a date and time. Thanks for using this tutorial to set a date and time on your AlmaLinux OS 10 system. For additional help or useful information, we recommend you check the official AlmaLinux website.