147

Is there a way to check which time zone I'm currently in on Linux?

15 Answers 15

24

Usually, the TZ environment variable will tell you something useful. However, it is best to use functions such as mktime() and localtime() to convert between time_t and a local timezone representation. That is, don't try to do the conversion yourself.

| improve this answer | |
  • 2
    is there any Command that tells about timezone the user is in? – Hussy Hussain Jul 11 '11 at 5:00
  • 29
    Sure, date will tell you. – Greg Hewgill Jul 11 '11 at 5:01
  • i have two instance of server , if i give "date" command in both server it shows different time. time zone for both server is IST, time of one server: Mon Jul 11 10:39:31 IST 2011 and other server Mon Jul 11 10:35:31 IST 2011 .. there is a difference of 4 minutes – Hussy Hussain Jul 11 '11 at 5:06
  • 10
    On Precise Pangolin echo $TZ returns nothing for me. – Iain Samuel McLean Elder Oct 5 '13 at 19:48
  • 3
    @GregHewgill your answer is not helpful at first view. Consider editing your answer please. See the most voted answer below. I will downvote your answer for now. Also there is no TZ env on default on my machines. – therealmarv Jun 21 '16 at 15:52
270

If you mean from the console, just type:

date +%Z
| improve this answer | |
  • good point... changed the answer to that effect – Rasman Jun 19 '14 at 15:44
  • And to set the timezone from the command line in Ubuntu, the following link provides the trivial, 1-line command to do so: askubuntu.com/a/524362/182454 – Dan Nissenbaum Dec 15 '16 at 6:30
  • This gives +07 for me. To get Region/City on a Debian / Arch based Linux, see this answer. – Tom Hale Jun 26 '18 at 6:55
64

If you want the numeric timezone:

date +'%:z %Z'

Sample output:

-05:00 EST
| improve this answer | |
  • 8
    On OS X this outputs :z EST – suspectus Feb 13 '15 at 17:01
  • 8
    This if for linux. – Paul Vargas Feb 13 '15 at 17:18
  • 1
    More precisely, this applies to GNU date. The BusyBox version prints something non-sensical, "%:z CEST" in my case. – Léo Lam Jun 3 '15 at 18:42
  • However, date +%z works fine on OS X. I suggest you modify the answer. – Neil Mayhew Aug 14 '15 at 17:22
  • 1
    Hi, @NeilMayhew Thanks! Humm... but the question has the tags linux ubuntu-10.04 – Paul Vargas Aug 14 '15 at 17:29
26

I wanted to find the timezone in "US/Eastern" or "Europe/London" form instead. You can find this in:

  • /etc/timezone (present on Ubuntu and Red Hat? but not e.g. Amazon Linux)
  • (on Red Hat style systems) as ZONE="US/Eastern" in /etc/sysconfig/clock
  • or you can try and match /etc/localtime to one of the files under /usr/share/zoneinfo; annoyingly this doesn't seem to be a symlink, but you can e.g.

    cd /usr/share/zoneinfo
    find * -type f -exec sh -c "diff -q /etc/localtime '{}' > /dev/null && echo {}" \;

    to find matching files - there's probably better ways to do that, but that works. There will be multiple matches.

| improve this answer | |
  • 5
    find /usr/share/zoneinfo/ -type f| xargs md5sum | grep $(md5sum /etc/localtime | cut -d' ' -f1) – freiheit Jul 4 '16 at 18:25
14

For ubuntu try this :

$ cat /etc/timezone

Sample output :

Asia/Kolkata

For other distro Reference : https://unix.stackexchange.com/questions/110522/timezone-setting-in-linux

| improve this answer | |
9

Sometimes you may be looking for the canonical timezone rather than the short form as produced by date %Z e.g. US/Eastern. On systems with timedatectl e.g. Fedora, timedatectl outputs lots of useful information, including the current zone:

# timedatectl
      Local time: Tue 2016-09-13 17:10:26 EDT
  Universal time: Tue 2016-09-13 21:10:26 UTC
        RTC time: Tue 2016-09-13 21:10:26
       Time zone: US/Eastern (EDT, -0400)
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no

Unfortunately, timedatectl takes set-timezone as a command, but has no corresponding get-timezone. Parse it as follows:

# timedatectl status | grep "zone" | sed -e 's/^[ ]*Time zone: \(.*\) (.*)$/\1/g'`
US/Eastern
| improve this answer | |
4
$ strings /etc/localtime | tail -n 1
MST7MDT,M3.2.0,M11.1.0

So I'm on Mountain Time. Although advices above on using environment variable or just date command output sometimes work better, depending how you want to use that.

| improve this answer | |
4

For the time zone, you can use geolocation:

$ curl https://ipapi.co/timezone
America/Chicago

Or:

$ curl http://ip-api.com/line?fields=timezone
America/Chicago

http://wiki.archlinux.org/index.php/time#Time_zone

| improve this answer | |
  • Just want to point out that although this will likely return the correct timezone the server is located at it does not necessarily return the timezone the server is configured for. – Art Geigel Sep 3 at 12:11
2
  • /etc/sysconfig/clock sets whether the hardware clock is stored as UTC or local time.
  • Symlink /etc/localtime to /usr/share/zoneinfo/... to set your timezone.
  • Type /sbin/hwclock --systohc [--utc] to set the hardware clock.

The Linux kernel always stores and calculates time as the number of seconds since midnight of the 1st of January 1970 UTC regardless of whether your hardware clock is stored as UTC or not. Conversions to your local time are done at run-time. One neat thing about this is that if someone is using your computer from a different timezone, they can set the TZ environment variable and all dates and times will appear correct for their timezone.

If the number of seconds since the 1st of January 1970 UTC is stored as an signed 32-bit integer (as it is on your Linux/Intel system), your clock will stop working sometime on the year 2038. Linux has no inherent Y2K problem, but it does have a year 2038 problem. Hopefully we'll all be running Linux on 64-bit systems by then. 64-bit integers will keep our clocks running quite well until aproximately the year 292271-million.

| improve this answer | |
2

I have linux mint Cinnamon. timedatectl gave the information I needed:

                  Local time: Mon 2020-06-29 11:04:27 PDT
              Universal time: Mon 2020-06-29 18:04:27 UTC
                    RTC time: Mon 2020-06-29 18:04:27
                   Time zone: America/Vancouver (PDT, -0700)
   System clock synchronized: yes

systemd-timesyncd.service active: yes RTC in local TZ: no

| improve this answer | |
1

A couple of solutions:

date +"%Z %z"
timedatectl | grep "Time zone"
cat /etc/timezone

gave me (respectively):

UTC +0000
Time zone: Etc/UTC (UTC, +0000)
Etc/UTC

My computer is on UTC.

| improve this answer | |
0

Using TZ or date IS NOT RELIABLE because it tells you the USER's timezone, not the default system timezone.

The default system timezone is stored in /etc/timezone (which is often a symbolic link to the timezone data file specific to the timezone). If you do not have an /etc/timezone, look at /etc/localtime. Generally that is the "server's" timezone. /etc/localtime is often a symlink to a timezone file in /usr/share/zoneinfo. That path to the correct timezone file will often give you geography information as well.

Newer linux have "timedatectl" which gives you tons of info when the command is run.

(as a side-node, if you have an ancient system that still uses the OLD hard-coded timezones, you can probably copy a modern timezone file onto it and it will work. I have had to do this many times to resolve changing timezones on older equipment).

| improve this answer | |
0

Sometimes timedatectl set-timezone doesn't update /etc/timezone, so it's best to get the tiemzone from the name of the file that the symlink /etc/timezone points to:

#!/bin/bash
set -euo pipefail

if filename=$(readlink /etc/localtime); then
    # /etc/localtime is a symlink as expected
    timezone=${filename#*zoneinfo/}
    if [[ $timezone = "$filename" || ! $timezone =~ ^[^/]+/[^/]+$ ]]; then
        # not pointing to expected location or not Region/City
        >&2 echo "$filename points to an unexpected location"
        exit 1
    fi
    echo "$timezone"
else  # compare files by contents
    # https://stackoverflow.com/questions/12521114/getting-the-canonical-time-zone-name-in-shell-script#comment88637393_12523283
    find /usr/share/zoneinfo -type f ! -regex ".*/Etc/.*" -exec \
        cmp -s {} /etc/localtime \; -print | sed -e 's@.*/zoneinfo/@@' | head -n1
fi

References: in this answer.

| improve this answer | |
0

You can show date and the timezone concurrently:

date +'%d/%m/%Y  %H:%M:%S [%:z  %Z]'
| improve this answer | |
0

All of the following solutions will give you an IANA compatible Olson timezone ID (e.g. America/Los_Angeles). However, some may return extra whitespace at the end.

Using the environment

The environment variable TZ contains* the timezone. Checking this is optimal if you're concerned with establishing a protocol between an application and a user.

$ echo $TZ

I can personally confirm that this works on at least two of my modern Linux computers, and is a very good variable to check first.

Using timedatectl and sed

Improvement upon Raman's answer, but without the useless use of grep. This solution is optimal on systems utilizing SystemD, as many modern Linux distros do.

$ timedatectl | sed -n 's/^\s*Time zone: \(.*\) (.*/\1/p'

Using /etc/timezone

This is a simple readable file, but doesn't seem to be available on as many distros anymore. IIRC, this is something those Debian devs came up with a while ago that fell out of favour.

$ cat /etc/timezone

Using GNU realpath because /etc/localtime is a symlink

This solution is optimal if you know that /etc/localtime is a symlink, which is something that both a lot of older software and guides accomplish and even modern SystemD promises; and you also have GNU realpath available, which should also be available on every GNU OS distro.

$ realpath --relative-to /usr/share/zoneinfo /etc/localtime

D'oh! /etc/localtime isn't a symlink; using find, sed, md5sum

If you find yourself with a non-symlink /etc/localtime, you can try to locate its md5 match in your local timezone database. This may return multiple matches as there are quite a few aliases in the Olson database.

$ find /usr/share/zoneinfo -type f -exec md5sum {} + |\
  sed /$(printf $(md5sum /etc/localtime))/'!d;s/.\{54\}//;/^posix/d'

If you'd only like a single timezone ID returned (whichever one Chourst entropy decides upon), you can use sed's q command to quit after the first match. This is much more performant than starting up head for instance. However, this causes find to break the pipe with md5sum early, causing an error to print to fd 2. You may ignore this error by piping it to /dev/null, like so:

$ find /usr/share/zoneinfo -type f -exec md5sum {} + 2> /dev/null |\
  sed /$(printf $(md5sum /etc/localtime))/'!d;s/.\{54\}//;/^posix/d;q'

Using curl and geolocation

If for some reason you don't want or don't trust the host's configuration, but you're certain that it can connect to the wider world web, there are several free, online services that will geolocate you (while they last). Below are some examples:

$ curl -Lsf https://ipapi.co/timezone

$ curl -Lsf http://ip-api.com/line?fields=timezone

$ curl -Lsf https://ipwhois.app/line/?objects=timezone

First two services shamelessly stolen from Steven Penny's answer.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy