Hi Paul, We do have the EST file. However, when we run zdump on it, it just displays the entry for 1901 and 2038 zdump -v /usr/share/zoneinfo/EST /usr/share/zoneinfo/EST Fri Dec 13 20:45:52 1901 UTC = Fri Dec 13 15:45:52 1901 EST isdst=0 gmtoff=-18000 /usr/share/zoneinfo/EST Sat Dec 14 20:45:52 1901 UTC = Sat Dec 14 15:45:52 1901 EST isdst=0 gmtoff=-18000 /usr/share/zoneinfo/EST Mon Jan 18 03:14:07 2038 UTC = Sun Jan 17 22:14:07 2038 EST isdst=0 gmtoff=-18000 /usr/share/zoneinfo/EST Tue Jan 19 03:14:07 2038 UTC = Mon Jan 18 22:14:07 2038 EST isdst=0 gmtoff=-18000 Because of above, we don’t get any DST changes applicable for EST for 2019. Is the output expected (which looks like as per https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)? Any idea since when it changed or was it this way all the time. Regards, Prakash -----Original Message----- From: Paul Eggert <eggert@cs.ucla.edu> Sent: Thursday, May 9, 2019 10:23 AM To: Manjusri Mahendran -X (manjmahe - INFOSYS LIMITED at Cisco) <manjmahe@cisco.com>; Matt Johnson <mj1856@hotmail.com> Cc: Time Zone Mailing List <tz@iana.org>; Prakash Mishra -X (prakasmi - INFOSYS LIMITED at Cisco) <prakasmi@cisco.com> Subject: Re: [tz] Issue with EST timezone Manjusri Mahendran -X (manjmahe - INFOSYS LIMITED at Cisco) wrote:
Looks like this issue is seen since OS RPM from Redhat "tzdata" is missing rules for EST timezone.
That's odd, as the tzdata package has the EST file on all the Red Hat machines I just now checked: On RHEL 6.10: $ rpm -qf /usr/share/zoneinfo/EST tzdata-2018i-1.el6.noarch On RHEL 7.6: $ rpm -qf /usr/share/zoneinfo/EST tzdata-2018i-1.el7.noarch On Fedora 30: $ rpm -qf /usr/share/zoneinfo/EST tzdata-2019a-1.fc30.noarch Perhaps your installation went haywire somehow?