- Code: Select all
apr 22 11:18:58 aspire7-kajsa systemd-networkd[809]: ** dont mind it said on this line, just see the time stamp **
apr 22 11:39:18 aspire7-kajsa systemd-timesyncd[997]: System clock time unset or jumped backwards, restored from recorded timestamp: Mon 2024-04-22 11:39:18 CEST
apr 22 11:39:18 aspire7-kajsa systemd-timesyncd[997]: The system is configured to read the RTC time in the local time zone. This mode cannot be fully supported. All system time to RTC updates are disabled.
So it seems that in beginning of booting system use hardware clock which is 21 minutes behind, then something suddenly realise it is wrong and correct it from then on.
As the last cited journal line say, should we change our installer so it always sets up systems to UTC instead (or what is the opposite of local time here)?
I understand the difference may confuse some programs
- Code: Select all
[kajsa@aspire7-kajsa ~]$ date ; sudo hwclock -r
mån 22 apr 2024 11:53:23 CEST
2024-04-22 11:32:37.253448+02:00
For now, i set hwclock to system time:
- Code: Select all
[kajsa@aspire7-kajsa ~]$ sudo hwclock -w
And now time corresponds
- Code: Select all
[kajsa@aspire7-kajsa ~]$ date ; sudo hwclock -r
mån 22 apr 2024 12:25:11 CEST
2024-04-22 12:25:11.374088+02:00
But apparently it may drift off far. How to avoid that?