Control: tag -1 moreinfo On Fri, 2015-07-03 at 16:27 +0200, Vincent Lefevre wrote: > Package: src:linux > Version: 3.16.7-ckt11-1 > Severity: important > > According to > > http://lists.freedesktop.org/archives/systemd-devel/2011-May/002526.html > > referenced by > > http://www.freedesktop.org/wiki/Software/systemd/timedated/ > > the Linux kernel syncs the system clock to the RTC every 11 minutes: > > At shutdown we no longer invoke "hwclock --systohc", i.e. do not write > the system clock back to the RTC. Why? In general there's not really a > reason to assume that the system clock was anymore correct than the RTC > so it's probably a good idea to leave the RTC untouched. The only time > when the system clock is probably very reliable is when NTP is used, but > in that case the kernel syncs the system clock to the RTC clock anyway > every 11 minutes, hence doing this in userspace is pointless. [...] > > but this doesn't work: after a reboot, the clock can be wrong (e.g. > 20 seconds late), so that it takes hours to get it corrected by NTP. > > Note: when I run "hwclock --systohc" manually before the reboot, the > clock is correct just after the reboot. Thus this is not a hardware > problem. Which NTP implementation are you using? Ben. -- Ben Hutchings Logic doesn't apply to the real world. - Marvin Minsky
Attachment:
signature.asc
Description: This is a digitally signed message part