When I do who -b; uptime I get system boot 2021-10-12 17:05 16:36:09 up 30 min, 1 user, load average: 0.00, 0.00, 0.00 As you can see the boot time reported by the last command is ahead. I have noted it is one hour ahead after a reboot. I have checked the system time in the BIOS before booting Linux and it is correct. -- Gerard Hooton.
Hi,> When I do who -b; uptime I get > > system boot 2021-10-12 17:05 > 16:36:09 up 30 min, 1 user, load average: 0.00, 0.00, 0.00 > > As you can see the boot time reported by the last command is ahead. > I have noted it is one hour ahead after a reboot. > > I have checked the system time in the BIOS before booting Linux and it is > correct.I don't know how exactly it comes but I guess it has something to do with local vs. system time. You have UTC as timezone but because of DST it's one hour apart. What does last report? On my test system I find the reboot which is shown in the who -b output in the last output, and the uptime reported by last again matches with the uptime output. Regards, Simon
> On 12.10.2021, at 17:41, Hooton, Gerard <g.hooton at ucc.ie> wrote: > > When I do who -b; uptime I get > > system boot 2021-10-12 17:05 > 16:36:09 up 30 min, 1 user, load average: 0.00, 0.00, 0.00 > > As you can see the boot time reported by the last command is ahead. > I have noted it is one hour ahead after a reboot. > > I have checked the system time in the BIOS before booting Linux and it is correct.What do you mean with ?correct?? UTC or localtime? For me timedatectl gives me ``` $ timedatectl ? RTC in local TZ: no ? ``` Which means that RTC/BIOS clock is in UTC, so when booting the timezone offset is added. I heard that dual boot with Windows makes problems because Windows is setting RTC always with local time. In that case try "RTC in local TZ: yes" Do you dualboot? What is timedatectl telling you? Best Regards, Markus