by mcloaked » Sat Nov 04, 2017 3:14 pm
Interestingly the following command shows the RTC is set correctly (though on one machine I have to manually set the system clock with the date command, and then write the time to the RTC with hwclock --systohc, and then I see:
$this->bbcode_second_pass_code('', '
# timedatectl status
Local time: Sat 2017-11-04 15:10:37 GMT
Universal time: Sat 2017-11-04 15:10:37 UTC
RTC time: Sat 2017-11-04 15:10:12
Time zone: Europe/London (GMT, +0000)
System clock synchronized: yes
systemd-timesyncd.service active: no
RTC in local TZ: no
')
Also
$this->bbcode_second_pass_code('', '
# hwclock --debug
hwclock from util-linux 2.31
System Time: 1509807955.224164
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Last drift adjustment done at 1509807734 seconds after 1969
Last calibration done at 1509807734 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
hwclock: ioctl(3, RTC_UIE_ON, 0) to /dev/rtc0 failed: Invalid argument
...synchronization failed
')
So I wonder if there was a regression with the hwclock command in the package util-linux?