[sf-lug] timezones, --> PST, etc. Re: Four mentionable matters, including SF-LUG mtg notice

Michael Paoli michael.paoli at berkeley.edu
Thu Oct 29 02:44:57 PDT 2026


On Thu, Oct 29, 2026 at 12:34 AM aaronco36 <aaronco36 at sdf.org> wrote:
> B. This Sunday morning of November 1st is the clock change to Standard
> Time; that is, to _Pacific_ Standard Time a.k.a. PST for we Californians.

Matters quite automagic for *nix, e.g. Linux.
$ (for TZ in {,right/}{PST8PDT,US/Pacific}; do zdump -v "$TZ" | sed
-ne '/2026/!d;/Mar/d;p'; done)
PST8PDT  Sun Nov  1 08:59:59 2026 UT = Sun Nov  1 01:59:59 2026 PDT
isdst=1 gmtoff=-25200
PST8PDT  Sun Nov  1 09:00:00 2026 UT = Sun Nov  1 01:00:00 2026 PST
isdst=0 gmtoff=-28800
US/Pacific  Sun Nov  1 08:59:59 2026 UT = Sun Nov  1 01:59:59 2026 PDT
isdst=1 gmtoff=-25200
US/Pacific  Sun Nov  1 09:00:00 2026 UT = Sun Nov  1 01:00:00 2026 PST
isdst=0 gmtoff=-28800
right/PST8PDT  Sun Nov  1 08:59:59 2026 UT = Sun Nov  1 01:59:59 2026
PDT isdst=1 gmtoff=-25200
right/PST8PDT  Sun Nov  1 09:00:00 2026 UT = Sun Nov  1 01:00:00 2026
PST isdst=0 gmtoff=-28800
right/US/Pacific  Sun Nov  1 08:59:59 2026 UT = Sun Nov  1 01:59:59
2026 PDT isdst=1 gmtoff=-25200
right/US/Pacific  Sun Nov  1 09:00:00 2026 UT = Sun Nov  1 01:00:00
2026 PST isdst=0 gmtoff=-28800
$ find /usr/share/zoneinfo -follow -type f -print | wc -l
1205
$
Not uncommonly supports thousands of timezones,
in fact even arbitrary, with POSIX:
$ zdump -v FOO5:15BAR+00:30,M4.5.0,M10,5,0 | sed -ne '/2026/!d;p'
FOO5:15BAR+00:30,M4.5.0,M10,5,0  Sun Apr 26 07:14:59 2026 UT = Sun Apr
26 01:59:59 2026 FOO isdst=0 gmtoff=-18900
FOO5:15BAR+00:30,M4.5.0,M10,5,0  Sun Apr 26 07:15:00 2026 UT = Sun Apr
26 06:45:00 2026 BAR isdst=1 gmtoff=-1800
FOO5:15BAR+00:30,M4.5.0,M10,5,0  Sun Oct  4 00:29:59 2026 UT = Sat Oct
 3 23:59:59 2026 BAR isdst=1 gmtoff=-1800
FOO5:15BAR+00:30,M4.5.0,M10,5,0  Sun Oct  4 00:30:00 2026 UT = Sat Oct
 3 19:15:00 2026 FOO isdst=0 gmtoff=-18900
$
But POSIX TZ doesn't handle multiple rules in a single TZ setting,
e.g. different rules for various times in past/future,
whereas timezone files do handle that.  Some jurisdictions even change
laws for timezone changes on quite short notice,
but fairly easy to accommodate that quickly with updates to timezone
files ... that's also why there are typically many timezone
file updates per year.

And of course best hardware clock discipline for *nix is UTC,
and can always do whatever one wishes with TZ (as can each user, etc.
on a host).
Some of the hazards with hardware clock not being UTC are, e.g.
multiple OSes (whatever they are)
on the hardware, and each trying to play "top dog" with the hardware clock, and
adjusting if forwards/backwards with transitions to/from Daylight
Saving / Summer time,
and tracking if they've already done that or not, and having no clue
about what other OSes
may do in such regards.  UTC for all avoids that entire mess.
Note also, UTC quite suggested for logs.  E.g. ever have a significant
security incident,
many that might otherwise well assist with analyzing logs, will refuse
to deal with logs that aren't UTC.

And of course NTP is good for keeping things well synced.
$ ntpq -nc peers | awk '{if($3 !~ /^16$/)print;}'
     remote           refid      st t when poll reach   delay   offset   jitter
===============================================================================
 172.104.209.204 168.61.215.74    5 u   7d 1024    0  80.6917   0.9639   0.0000
 24.144.88.190   132.163.96.3     2 u  80d 1024    0  13.5879  21.2737   0.0000
*23.143.196.203  129.134.27.123   2 u  191 1024  377  15.1504   1.5714   2.3005
+66.244.16.123   66.244.0.68      2 u  499 1024  377  20.4706   0.8429   0.7546
+2602:fd01:40:80 66.244.0.68      2 u   42 1024  377  23.1852   0.1792   0.8965
+2606:82c0:22::e 218.73.139.35    2 u  734 1024  377  81.6680   0.1164   2.8554
-5.254.77.191    216.239.35.0     2 u  781 1024  377  70.5407  -0.9190   2.7366
$

And of course SF-LUG web page automatically updates its meeting schedule.
And no PHP - dispensed with that quite a while back for that page.
$ hostname && id && crontab -l
balug-sf-lug-v2.balug.org
uid=22035(sflugwww) gid=22035(sflugwww) groups=22035(sflugwww)
0,30 * * * * "$HOME"/bin/update_meeting_schedule >>/dev/null 2>&1; :
$
https://www.sf-lug.org/~sflugwww/bin/update_meeting_schedule
It checks twice per hour, and updates as appropriate,
and it doesn't care about what the host's default timezone is - not
really relevant.
Suppose could even do, instead of crontab job, a self-rescheduling at(1) job,
but that might be wee bit more confusing for those maintaining it -
crontab job is quite good enough.



More information about the sf-lug mailing list