Lew Pitcher
2020-10-12 01:06:11 UTC
I run 32bit Slackware 14.0 on one of my systems, and apply relevant
patches from Slackware when they become available. This afternoon, I
applied (using upgradepkg) the recent glibc-zoneinfo-2020b-
noarch-1_slack14.0 the over an existing (and working) glibc-
zoneinfo-2020a-noarch-1_slack14.0.
My motherboard RTC is set to UTC, as are the /etc/hardwareclock
parameters, and the /etc/localtime is copied from /usr/share/zoneinfo/
EST5EDT (and /etc/localtime-copied-from points to /usr/share/zoneinfo/
EST5EDT).
So, I was surprised at 8PM EDT tonight when a cron job scheduled for
midnight ran to completion. Once I gathered my whits, I checked the
system clock, which confirmed that as of 8PM wallclock time, the sytem
registered midnight. Both /etc/localtime and /etc/localtime-copied-from
were present, and /etc/localtime-copied-from pointed to the EST5EDT
zoneinfo file.
I immediately suspected the 2020b zoneinfo update, and reversed it out
(reapplying via upgradepkg the glibc-zoneinfo-2020a-noarch-1_slack14.0
patch.
With that done, the system correctly showed the wallclock time (now, just
past 8:30PM).
File tells me that the 2020b EST5EDT is:
timezone data, version 2, no gmt time flags, no std time flags,
no leap seconds, no transition times, 1 abbreviation char
and the 2020a EST5EDT is
timezone data, version 2, 5 gmt time flags, 5 std time flags,
no leap seconds, 149 transition times, 5 abbreviation chars
A properly updated 64bit 14.2 system, still showing the proper wallclock
time gives me, for the 2020b EST5EDT
timezone data, version 2, no gmt time flags, no std time flags,
no leap seconds, no transition times, 1 abbreviation char
So, a cautionary note: the glibc-zoneinfo-2020b-noarch-1_slack14.0
upgrade changed something radically. If you run 14.0, check that your
timezone data still applies properly after the upgrade.
patches from Slackware when they become available. This afternoon, I
applied (using upgradepkg) the recent glibc-zoneinfo-2020b-
noarch-1_slack14.0 the over an existing (and working) glibc-
zoneinfo-2020a-noarch-1_slack14.0.
My motherboard RTC is set to UTC, as are the /etc/hardwareclock
parameters, and the /etc/localtime is copied from /usr/share/zoneinfo/
EST5EDT (and /etc/localtime-copied-from points to /usr/share/zoneinfo/
EST5EDT).
So, I was surprised at 8PM EDT tonight when a cron job scheduled for
midnight ran to completion. Once I gathered my whits, I checked the
system clock, which confirmed that as of 8PM wallclock time, the sytem
registered midnight. Both /etc/localtime and /etc/localtime-copied-from
were present, and /etc/localtime-copied-from pointed to the EST5EDT
zoneinfo file.
I immediately suspected the 2020b zoneinfo update, and reversed it out
(reapplying via upgradepkg the glibc-zoneinfo-2020a-noarch-1_slack14.0
patch.
With that done, the system correctly showed the wallclock time (now, just
past 8:30PM).
File tells me that the 2020b EST5EDT is:
timezone data, version 2, no gmt time flags, no std time flags,
no leap seconds, no transition times, 1 abbreviation char
and the 2020a EST5EDT is
timezone data, version 2, 5 gmt time flags, 5 std time flags,
no leap seconds, 149 transition times, 5 abbreviation chars
A properly updated 64bit 14.2 system, still showing the proper wallclock
time gives me, for the 2020b EST5EDT
timezone data, version 2, no gmt time flags, no std time flags,
no leap seconds, no transition times, 1 abbreviation char
So, a cautionary note: the glibc-zoneinfo-2020b-noarch-1_slack14.0
upgrade changed something radically. If you run 14.0, check that your
timezone data still applies properly after the upgrade.
--
Lew Pitcher
"In Skills, We Trust"
Lew Pitcher
"In Skills, We Trust"