Improve UX when hardware clock is set to localtime in a timezone too far from UTC
There’s no general solution to the “software tends to break when system time goes backwards” well-known class of problems. Given we have to set the system clock correctly and we cannot easily guess whether the hardware clock (RTC) is in localtime or UTC, it seems unavoidable that we will trigger all kinds of problems for users with a RTC set to localtime in a timezone >> UTC, e.g. #14250 (closed) and #15548.
What we could do to mitigate the problem a bit:
- done: Document how to set the RTC to UTC. This is the default on most Linux and macOS but Windows defaults to localtime. https://wiki.archlinux.org/index.php/System_time#UTC_in_Windows explains how to fix that for Windows 7 and newer; on older Windows it seems to be a lost case.
- Anything else?