> For instance, your computer could set your clock for you
> fully automatically, if it knew where you were.
That, of course, would require a "public IP" address.
Potentially doable with IPv6, if it were fully supported. My ISP
doesn't support it, at all.
And, not to mention, even if one has a "public IP" address,
would happen if one is using time-sync and then periodically connects
to a VPN. Wouldn't that be fun trying to look through
logs with time changes? :-)
Actually this brings up a good point, hence my replying to an old
Logs should be *made* in GMT/UTC, so they always have an absolutely
fixed time (e.g. no trying to work out which 1:30 am that a logged item
refers to on daylight saving's day). But the log results should be
*displayable* in local time, so that you can follow them easily.
Though the catch is, you need to be able to display them in the local
time that they were created in.
e.g. You know that at 8 pm last week when you were in London you did
this thing, and you did something at 5 pm when in Melbourne last month.
And you want to read your logs showing that kind of thing (8 and 5 pm),
instead of having to do maths for the different timezone changes.
It's doable, but only if the logs are written with *full* time and date
Linux 3.10.0-1062.4.1.el7.x86_64 #1 SMP Fri Oct 18 17:15:30 UTC 2019 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.