So, I'll be changing ISP (at least for IPv4) ...
that'll mean new IPs for IPv4 ... most notably for these [L]UG domains
(and in general subdomains thereof):
balug.orgsf-lug.orgsflug.orgsflug.comsflug.netsf-lug.netsf-lug.comberkeleylug.comberkeleylug.org
A bit more generally:
By not later than end of 2019-12-19, these IPv4 IPs (range) will be
"going away"/changing:
198.144.194.232/29 198.144.194.232 - 198.144.194.239
198.144.194.232
198.144.194.233
198.144.194.234
198.144.194.235
198.144.194.236
198.144.194.237
198.144.194.238
198.144.194.239
At present, my IPv6 is provided from another ISP (tunneled via IPv4),
so I'm expecting the IPv6 IPs will remain the same (at least through
this transition anyway).
Anyway, hopefully all these changes will happen rather to quite smoothly
... but a bit early to say. E.g., as I transition ISPs, there may be
brief(ish) period between, when temporarily neither is available.
We shall see. I'll update relevant contatct(s)/lists as/when
relevant and appropriate and I'm reasonably able to do so.
Hopefully I can minimize any "user facing" impact ... if I'm
reasonably lucky, may be able to do it quite seamlessly, with
essentially no impact to "users" ... we shall see.
references/excerpts:
http://linuxmafia.com/pipermail/conspire/2019-November/009966.html
The BALUG Wiki is "temporarily" (mostly) down for a bit.
I'm integrating WordPress (not for BALUG, but for BerkeleyLUG)
on same host & server ... that required web server to use newer
php version to work with WordPress ... which has "temporarily"
(mostly) broken the BALUG Wiki.
Index pages themselves still appear to work, e.g.:
https://www.wiki.balug.org/wiki/doku.php?do=index&idx=balug
but contents pages, e.g.:
https://www.wiki.balug.org/wiki/doku.php?id=balug:cds_and_images_etc
presently fail.
I'm hoping/presuming it's just some config bit(s) I need to track down
and correct/adjust, then all should be fine again.
Unless someone convinces me otherwise (unlikely),
I'll probably proceed fairly soon, to reconfigure the
BALUG VM (Virtual Machine) - (host balug-sf-lug-v2.balug.org)
and likewise "vicki" (hostname vicki - and the sometimes /
semi-regular physical host of the BALUG VM)
to default to using UTC.
To minimize surprises/disruptions - in addition to this notice,
I'll probably make that change upon a (re)boot of those hosts
(e.g. on reboot, go to single user mode, reconfigure,
then reboot per normal to multi-user).
Rationale:
o security, etc. - many won't even consider looking at logs if they're
not in UTC
o no matter who uses it from where on the planet, one zone all can (well
approximately) reasonably agree upon
o no need/reason to change it in the (unlikely) even it moves to another
physical location, or timezone at existing physical location changes
o "principle of least surprise" - if it was a whole bunch 'o local folks
doing admin, etc. on the box, and especially more "jr." folks, local
would be of least surprise. But alas, yours truly does >>~=99.7 %
of the systems administration, etc. on those hosts, so that being
the case, and having been the case quite a while, and seeming improbable
to change ... for me, that "principle of least surprise", and other
reasons/advantages ... UTC
o Users can always use TZ setting to whatever they wish that's available,
we're only talking about the system default timezone, e.g.:
$ TZ=America/Los_Angeles; export TZ