For anyone having problems with the clock on their computer following the clocks going forward on Saturday, check which timezone you have set;
# timedatectl
Local time: Tue 2024-04-02 12:06:00 UTC
Universal time:...
For anyone having problems with the clock on their computer following the clocks going forward on Saturday, check which timezone you have set;
# timedatectl
Local time: Tue 2024-04-02 12:06:00 UTC
Universal time: Tue 2024-04-02 12:06:00 UTC
RTC time: n/a
Time zone: Etc/UTC (UTC, +0000)
System clock synchronized: yes
NTP service: inactive
RTC in local TZ: no
If as in this example it’s showing UTC, your clock will be an hour our. To fix this, change your timezone to BST;
# timedatectl set-timezone Europe/London
# timedatectl
Local time: Tue 2024-04-02 13:11:35 BST
Universal time: Tue 2024-04-02 12:11:35 UTC
RTC time: n/a
Time zone: Europe/London (BST, +0100)
System clock synchronized: yes
NTP service: inactive
RTC in local TZ: no
Ans that should put things right.
Typically not an issue for desktop machines as they tend to let you choose your timezone as a part of the installation and setup procedure. If on the other hand you’re running a machine of virtual machine with a text console and a minimum install, it could well have defaulted to UTC (aka GMT).
1 post - 1 participant