[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ntpsec as server questions



On Wed, Dec 06, 2023 at 11:28:40AM -0500, Pocket wrote:
> diff /usr/share/zoneinfo/EST5EDT /usr/share/zoneinfo/America/New_York
> Binary files /usr/share/zoneinfo/EST5EDT and
> /usr/share/zoneinfo/America/New_York differ

unicorn:/usr/share/zoneinfo$ ls -l EST5EDT
-rw-r--r-- 1 root root 2310 May 28  2023 EST5EDT

unicorn:/usr/share/zoneinfo$ ls -l America/New_York 
-rw-r--r-- 1 root root 3552 May 28  2023 America/New_York

unicorn:/usr/share/zoneinfo$ file EST5EDT 
EST5EDT: timezone data (fat), version 2, 5 gmt time flags, 5 std time flags, no leap seconds, 149 transition times, 5 local time types, 16 abbreviation chars

unicorn:/usr/share/zoneinfo$ file America/New_York 
America/New_York: timezone data (fat), version 2, 6 gmt time flags, 6 std time flags, no leap seconds, 236 transition times, 6 local time types, 20 abbreviation chars

OK, they are definitely not the same.  I don't feel like digging through
them to try to figure out *what* the differences are, but clearly there
must be *some* point(s) in time where they give different results.

If you wish to continue using the legacy time zone, knowing that it's
different from the proper one (but not precisely in what way), then on
your own head be it.

For comparison, this one is cleary safe to use:

unicorn:/usr/share/zoneinfo$ ls -l US/Eastern
lrwxrwxrwx 1 root root 19 May 28  2023 US/Eastern -> ../America/New_York


Reply to: