The system time backed by the system clock is used in Unix systems to keep track of time. It can be set by a hardware clock or by an external time server.
- 1 Preface
- 2 Time zone
- 3 LC_TIME
- 4 System clock
- 5 Hardware clock
- 6 See also
- 7 External resources
Software clock vs Hardware clock
The system clock, provided by the kernel, is implemented as a simple count of the number of ticks that have transpired since the 1 January 1970 00:00:00 UTC. This is called Unix time.
The hardware clock (also known as real-time clock or RTC) is typically a component on the mainboard. It runs independent of the state of the operating system all the time, also when the computer is shutdown.
UTC time vs localtime
The time for hardware clock can be modified to represent two standards: localtime or UTC time. The localtime is the real time of the time zone including DST. Preferred is UTC time because the system time gets computed by adding the time zone difference and DST. So daylight saving changes get automatically applied and changing the time zone are possible without changing the hardware clock. Exceptions can be made when using a dual-boot system; this is when the other operating system does not support or is not configured for an UTC hardware clock (by default, Windows uses localtime).
In order to keep time properly, select the proper time zone so the system knows where it is located.
Look for the local time zone in /usr/share/zoneinfo. Please avoid the /usr/share/zoneinfo/Etc/GMT* time zones as their names do not indicate the expected zones. For instance, /usr/share/zoneinfo/Etc/GMT-8 is in fact GMT+8. For localtime select the "localtime" time zone.
After zone info has been selected, set the time zone in /etc/timezone, e.g. for Germany:
The information in this file is used by sys-libs/timezone-data on each package update to copy the chosen zoneinfo file to /etc/localtime. To setup this file out of order, run:
emerge --config timezone-data
systemd comes with the timedatectl to manage the time zone:
To check the current zone:
To list available zones:
To change the time zone, e.g. for Germany:
timedatectl set-timezone Europe/Berlin
Typically the system clock time is set up by the hardware clock on boot. Alternatively it is possible to manually set the system clock or use a network time server.
The date command can be used to manage the system clock time:
To check the current software clock time:
To set the system clock, e.g. 12:34, May. 6, 2016:
See the NTP article for information concerning the use of time servers.
systemd comes with the timedatectl command to manage the system clock time:
To check the current software clock time:
To set the system clock:
timedatectl set-time "2012-12-17 12:30:59"
To have a hardware clock, the following kernel options must be activated:
Device Drivers ---> [*] Real Time Clock ---> [ ] Set system time from RTC on startup and resume [ ] Set the RTC time based on NTP synchronization [*] /sys/class/rtc/rtcN (sysfs) [*] /proc/driver/rtc (procfs for rtc0) [*] /dev/rtcN (character devices) <*> PC-style 'CMOS'
At runtime, to check the current hardware clock time:
To set the hardware clock to the current system clock:
Syncing Hardware clock and System time
Typically the hardware clock is used to setup the system clock on boot. This can be done by the kernel itself or by a boot service (init script). Also on shutdown the kernel or a service can write the software clock to the hardware clock. This aids the system in having the correct time on boot.
On a sufficiently modern kernel (3.9 or newer), Linux can be configured to handle setting the system time automatically. To do so, also the Set system time ... and Set the RTC time ... drivers need to be activated:
Device Drivers ---> [*] Real Time Clock ---> [*] Set system time from RTC on startup and resume [*] Set the RTC time based on NTP synchronization [*] /sys/class/rtc/rtcN (sysfs) [*] /proc/driver/rtc (procfs for rtc0) [*] /dev/rtcN (character devices) <*> PC-style 'CMOS'
Please note that Set the RTC time based on NTP synchronization is not used by some NTP implementations. Supported NTP implementations include: net-misc/chrony (more information here) and net-misc/ntp (more information in the NTP article). OpenNtpd (net-misc/openntpd) does not support setting the hardware time and therefore should be avoided.
To check if the hardware time is updated, run:
adjtimex --print | grep status
The 64 bit of the reported number should be unset (0). More information in hwclock man pages (search '11 minute mode').
When using OpenRC the hwclock init script can set the system clock on boot and sync system time to the hardware clock on shutdown. The service is enabled by default and should be disabled in favor of the above mentioned in-kernel method. The hwclock script should not be run when using the kernel's real time clock.
rc-update del hwclock
If however there is a need for using the OpenRC, set both
YES in /etc/conf.d/hwclock. By default the service is configured for UTC time standard. To change to localtime add
clock_hctosys="YES" clock_systohc="YES" # clock="local"
Restart the hwclock service and have the hardware clock init script run on system boot:
rc-service hwclock restart
rc-update add hwclock boot
systemd can be used to set the system clock on boot. Use timedatectl to manage the hardware clock:
To check the current hardware clock time:
timedatectl | grep "RTC time"
To set the hardware clock to the current system clock (UTC time standard):
timedatectl set-local-rtc 0
To set the hardware clock to the current system clock (localtime time standard):
timedatectl set-local-rtc 1
- NTP - Another way to manage system time is through the network time protocol.
- OpenNTPD - Lightweight NTP server ported from OpenBSD
- http://lifehacker.com/5742148/fix-windows-clock-issues-when-dual-booting-with-os-x - Dual booting with MS Windows, set RealTimeIsUniversal. Also tested with Windows 10.
- http://tldp.org/HOWTO/Clock-2.html - The Clock Mini-HOWTO.