System time

This article or section needs expansion.

In an operating system, the time (clock) is determined by four parts: time value, whether it is local time or UTC or something else, time zone, and Daylight Saving Time (DST) if applicable. This article explains what they are and how to read/set them. Two clocks are present on systems: a hardware clock and a system clock which are also detailed in this article.

Standard behavior of most operating systems is:

• Set the system clock from the hardware clock on boot.
• Keep accurate time of the system clock, see #Time synchronization.
• Set the hardware clock from the system clock on shutdown.

Contents

Hardware clock

The hardware clock (a.k.a. the Real Time Clock (RTC) or CMOS clock) stores the values of: Year, Month, Day, Hour, Minute, and Seconds. Only 2016, or later, UEFI firmware has the ability to store the timezone, and whether DST is used.

Read hardware clock

Set hardware clock from system clock

The following sets the hardware clock from the system clock. Additionally it updates /etc/adjtime or creates it if not present. See hwclock(8) section «The Adjtime File» for more information on this file as well as the #Time skew section.

System clock

The system clock (a.k.a. the software clock) keeps track of: time, time zone, and DST if applicable. It is calculated by the Linux kernel as the number of seconds since midnight January 1st 1970, UTC. The initial value of the system clock is calculated from the hardware clock, dependent on the contents of /etc/adjtime . After boot-up has completed, the system clock runs independently of the hardware clock. The Linux kernel keeps track of the system clock by counting timer interrupts.

Read clock

To check the current system clock time (presented both in local time and UTC) as well as the RTC (hardware clock):

Set system clock

To set the local time of the system clock directly:

sets the time to May 26th, year 2014, 11:13 and 54 seconds.

Time standard

There are two time standards: localtime and Coordinated Universal Time (UTC). The localtime standard is dependent on the current time zone, while UTC is the global time standard and is independent of time zone values. Though conceptually different, UTC is also known as GMT (Greenwich Mean Time).

The standard used by the hardware clock (CMOS clock, the BIOS time) is set by the operating system. By default, Windows uses localtime, macOS uses UTC, and UNIX-like systems vary. An OS that uses the UTC standard will generally consider the hardware clock as UTC and make an adjustment to it to set the OS time at boot according to the time zone.

If multiple operating systems are installed on a machine, they will all derive the current time from the same hardware clock: it is recommended to adopt a unique standard for the hardware clock to avoid conflicts across systems and set it to UTC. Otherwise, if the hardware clock is set to localtime, more than one operating system may adjust it after a DST change for example, thus resulting in an over-correction; problems may also arise when traveling between different time zones and using one of the operating systems to reset the system/hardware clock.

The hardware clock can be queried and set with the timedatectl command. You can see the current hardware clock time standard of the Arch system using:

To change the hardware clock time standard to localtime, use:

To revert to the hardware clock being in UTC, type:

These generate /etc/adjtime automatically and update the RTC accordingly; no further configuration is required.

During kernel startup, at the point when the RTC driver is loaded, the system clock may be set from the hardware clock. Whether this occurs depends on the hardware platform, the version of the kernel and kernel build options. If this does occur, at this point in the boot sequence, the hardware clock time is assumed to be UTC and the value of /sys/class/rtc/rtcN/hctosys (N=0,1,2. ) will be set to 1.

Later, the system clock is set again from the hardware clock by systemd, dependent on values in /etc/adjtime . Hence, having the hardware clock using localtime may cause some unexpected behavior during the boot sequence; e.g system time going backwards, which is always a bad idea (there is a lot more to it). To avoid it systemd will only synchronize back, if the hardware clock is set to UTC and keep the kernel uninformed about the local timezone. As a consequence timestamps on a FAT filesystem touched by the Linux system will be in UTC.

UTC in Microsoft Windows

To dual boot with Windows it is recommended to configure Windows to use UTC, rather than Linux to use localtime. (Windows by default uses localtime [1].)

It can be done by a simple registry fix: Open regedit and add a DWORD value for 32-bit Windows, or QWORD for 64-bit one, with hexadecimal value 1 to the registry:

You can do this from an Administrator Command Prompt running:

(Replace QWORD with DWORD for 32-bit Windows.)

Alternatively, create a *.reg file (on the desktop) with the following content and double-click it to import it into registry:

(Replace qword with dword for 32-bit Windows.)

Should Windows ask to update the clock due to DST changes, let it. It will leave the clock in UTC as expected, only correcting the displayed time.

The #Hardware clock and #System clock time may need to be updated after setting this value.

If you are having issues with the offset of the time, try reinstalling tzdata and then setting your time zone again:

Historical notes

For really old Windows, the above method fails, due to Windows bugs. More precisely,

• Before Vista SP2, there is a bug that resets the clock to localtime after resuming from the suspend/hibernation state.
• For XP and older, there is a bug related to the daylight saving time. See [2] for details.
• For even older versions of Windows, you might want to read http://www.cl.cam.ac.uk/

mgk25/mswish/ut-rtc.html — the functionality was not even documented nor officially supported then.

For these operating systems, it is recommended to use localtime.

UTC in Ubuntu

Ubuntu and its derivatives have the hardware clock set to be interpreted as in «localtime» if Windows was detected on any disk during Ubuntu installation. This is apparently done deliberately to allow new Linux users to try out Ubuntu on their Windows computers without editing the registry.

For changing this behavior, see above.

Time zone

To check the current zone defined for the system:

To list available zones:

To set your time zone:

This will create an /etc/localtime symlink that points to a zoneinfo file under /usr/share/zoneinfo/ . In case you choose to create the link manually (for example during chroot where timedatectl will not work), keep in mind that it must be a symbolic link, as specified in archlinux(7) [dead link 2021-02-08] :

Setting based on geolocation

To set the timezone automatically based on the IP address location, one can use a geolocation API to retrieve the timezone, for example curl https://ipapi.co/timezone , and pass the output to timedatectl set-timezone for automatic setting. Some geo-IP APIs that provide free or partly free services are listed below:

Update timezone every time NetworkManager connects to a network

Alternatively, the tool tzupdate AUR automatically sets the timezone based on the geolocation of the IP address. This comparison of the most popular IP geolocation apis may be helpful in deciding which API to use in production.

Time skew

Every clock has a value that differs from real time (the best representation of which being International Atomic Time); no clock is perfect. A quartz-based electronic clock keeps imperfect time, but maintains a consistent inaccuracy. This base ‘inaccuracy’ is known as ‘time skew’ or ‘time drift’.

When the hardware clock is set with hwclock , a new drift value is calculated in seconds per day. The drift value is calculated by using the difference between the new value set and the hardware clock value just before the set, taking into account the value of the previous drift value and the last time the hardware clock was set. The new drift value and the time when the clock was set is written to the file /etc/adjtime overwriting the previous values. The hardware clock can therefore be adjusted for drift when the command hwclock —adjust is run; this also occurs on shutdown but only if the hwclock daemon is enabled, hence for Arch systems which use systemd, this does not happen.

If the hardware clock keeps losing or gaining time in large increments, it is possible that an invalid drift has been recorded (but only applicable, if the hwclock daemon is running). This can happen if you have set the hardware clock time incorrectly or your time standard is not synchronized with a Windows or macOS install. The drift value can be removed by first removing the file /etc/adjtime , then setting the correct hardware clock and system clock time. You should then check if your time standard is correct.

The software clock is very accurate but like most clocks is not perfectly accurate and will drift as well. Though rarely, the system clock can lose accuracy if the kernel skips interrupts. There are some tools to improve software clock accuracy:

Time synchronization

The Network Time Protocol (NTP) is a protocol for synchronizing the clocks of computer systems over packet-switched, variable-latency data networks. The following are implementations of NTP available for Arch Linux:

• Chrony — A client and server that is roaming friendly and designed specifically for systems that are not online all the time.

https://chrony.tuxfamily.org/ || chrony

• ConnMan — A lightweight network manager with NTP support.

https://01.org/connman || connman

• Network Time Protocol daemon — The reference implementation of the protocol, especially recommended to be used on time servers. It can also adjust the interrupt frequency and the number of ticks per second to decrease system clock drift, and will cause the hardware clock to be re-synchronised every 11 minutes.

http://www.ntp.org/ || ntp

• ntpclient — A simple command-line NTP client.

http://doolittle.icarus.com/ntpclient/ || ntpclientAUR

• NTPsec — A fork of NTPd, focused on security.

https://ntpsec.org/ || ntpsecAUR

• OpenNTPD — Part of the OpenBSD project and implements both a client and a server.

http://www.openntpd.org/ || openntpd

• sntp — An SNTP client that comes with NTPd. It supersedes ntpdate and is recommended in non-server environments.

http://www.ntp.org/ || ntp

• systemd-timesyncd — A simple SNTP daemon that only implements a client side, focusing only on querying time from one remote server. It should be more than appropriate for most installations.

https://www.freedesktop.org/wiki/Software/systemd/ || systemd

Per-user/session or temporary settings

For some use cases it may be useful to change the time settings without touching the global system values. For example to test applications relying on the time during development or adjusting the system time zone when logging into a server remotely from another zone.

To make an application «see» a different date/time than the system one, you can use the faketime (from libfaketime ) utility.

If instead you want an application to «see» a different time zone than the system one, set the TZ environment variable, for example:

This is different than just setting the time, as for example it allows to test the behavior of a program with positive or negative UTC offset values, or the effects of DST changes when developing on systems in a non-DST time zone.

Another use case is having different time zones set for different users of the same system: this can be accomplished by setting the TZ variable in the shell’s configuration file, see Environment variables#Defining variables.

Troubleshooting

Clock shows a value that is neither UTC nor local time

This might be caused by a number of reasons. For example, if your hardware clock is running on local time, but timedatectl is set to assume it is in UTC, the result would be that your timezone’s offset to UTC effectively gets applied twice, resulting in wrong values for your local time and UTC.

To force your clock to the correct time, and to also write the correct UTC to your hardware clock, follow these steps:

• Setup ntpd (enabling it as a service is not necessary).
• Set your time zone correctly.
• Run ntpd -qg to manually synchronize your clock with the network, ignoring large deviations between local UTC and network UTC.
• Run hwclock —systohc to write the current software UTC time to the hardware clock.

Tips and tricks

fake-hwclock

alarm-fake-hwclock designed especially for system without battery backed up RTC, it includes a systemd service which on shutdown saves the current time and on startup restores the saved time, thus avoiding strange time travel errors.

How to set or change a computer’s date and time

This page contains steps on how to change the computer’s date and time in the computer’s operating system, or in the BIOS settings. It also describes how to change the date and time on a mobile device.

If the date and time is resetting to an old date or the wrong time, the CMOS battery is bad and needs to be replaced. For help with CMOS battery issues, see: Why is computer asking for the time and date each time it boots?

If you are using Windows on a virtual machine, change the date and time on the host machine, not the virtual machine. The virtual machine gets the current date and time information from the host.

Setting the date and time in BIOS or CMOS setup

1. Open the CMOS setup.

• How to enter the BIOS or CMOS setup.

1. In the system setup menu, locate the date and time.
2. Using the arrow keys, navigate to the date or time, adjust them to your liking, and then select Save and Exit.

Steps may vary for your BIOS. For additional information, see: Computer BIOS help and support.

If, after rebooting the computer the date and time have to be set again, your CMOS battery is most likely bad, consider replacing the CMOS battery. See: How to replace the CMOS battery.

Setting date and time in the operating system

To change the system time in your operating system, follow these steps.

Windows 10

Windows 10 automatically adjusts your date and time for you and only allows you to adjust the time if you disable this feature. If the wrong date and time are set, or you need to change the time or time zone, follow the steps below.

1. Right-click or tap the date and time in the Windows Notification Area in the bottom-right corner of the screen.
2. Click Adjust date/time.
3. Make sure your Time zone is set properly if your computer is displaying the wrong time.
4. To manually adjust the time, turn off the Set time automatically option, then click the Change button.
5. Change the date or time as desired, then click the Change button.

There is no ability to add seconds to the time displayed in the Windows Notification Area on the Taskbar. However, if you click the date and time, a pop-up window opens and displays the time with seconds included.

Windows 8

1. Click or tap the date and time in the Windows Notification Area in the bottom-right corner of the screen.
2. Select Change date and time settings at the bottom of the window that appears (shown below).

1. In the Date and Time window, under the Date and Timetab, click the Change date and time button.
2. Make your adjustments and click OK.
3. Click OK on the main Date and Time window to save the changes.

There is no ability to add seconds to the time displayed in the Windows Notification Area on the Taskbar. However, if you click the date and time, a pop-up window opens and displays the time with seconds included.

To change the time zone, follow these steps.

1. In the Date and Time window from above, under the Date and Time tab, click the Change time zone button.
2. Select the new time zone in the Time zone drop-down field and click OK.
3. Click OK on the main Date and Time window to save the time zone change.

Windows 7 and Vista

In Windows 7 and Windows Vista, follow these steps to adjust the date and time.

1. Press Windows key + D or navigate to the Windows desktop.
2. Click or tap the date and time in the Windows Notification Area in the bottom-right corner of the screen.
3. Select Change date and time settings in the bottom of the window that appears (shown below).

1. In the Date and Time window, under the Date and Timetab, click the Change date and time button.
2. Make your adjustments and click OK.
3. Click OK on the Date and Time window to save the changes.

There is no ability to add seconds to the time displayed in the Windows Notification Area on the Taskbar. However, if you click the date and time, a pop-up window opens and displays the time with seconds included.

To change the time zone, follow these steps.

1. In the Date and Time window from above, under the Date and Time tab, click the Change time zone button.
2. Select the new time zone in the Time zone drop-down field and click OK.
3. Click OK on the main Date and Time window to save the time zone change.

Windows XP, 2000, 98, 95, NE, and NT 4

In Windows XP and earlier versions, follow these steps to set the date and time.

1. Navigate to the Windows desktop.
2. Right-click the time in your Systray, usually located at the bottom-right of your screen.
3. Click the Adjust Date/Time menu item.
4. This action opens the Date/Time Properties window, where you can adjust the date, time, and time zone.
5. Once the proper date and time are set, click Apply, and then Ok.

You may also double-click the time to open the Date/Time Properties window.

If you want to change how the computer handles daylight savings, click the Time Zone tab and check or uncheck the Automatically adjust clock for daylight saving changes option.

MS-DOS and Windows command line

Setting the date through MS-DOS or the Windows command line is accomplished via use of the date command. See our date command page for further information.

Setting the time through MS-DOS or the Windows command line is accomplished via use of the time command. See our time command page for further information.

Linux command line

In Linux, use the date command to manually set the system date and time.

Or, to synchronize your system clock with a network time server, use ntpdate . For example, on Ubuntu or Debian:

Specify a network time server to the ntpdate command, for example us.pool.ntp.org .

To keep your system time synchronized regularly, install the ntp system service.

The service starts immediately, and starts automatically at system boot. To configure the service, edit the file /etc/ntp.conf , then restart the service.

To access the hardware clock directly, use the hwclock command.

FreeBSD

In FreeBSD, ntp can be installed with the pkg package manager.

Setting the date and time on the Apple operating system

1. Open the Apple Menu and select System Preferences.
2. Click Date & Time, and then click Date & Time again.
3. In the Date & Time window, set the date, time, time zone.

Setting the date and time on a mobile device

To set the date and time on a mobile device, follow these steps.