2016-02-21 20:14 GMT+02:00 Andreas Henriksson <[email protected]>: > Hello Martin-Éric Racine. > > On Sun, Feb 21, 2016 at 05:17:30PM +0200, Martin-Éric Racine wrote: >> Package: util-linux >> Version: 2.27.1-3 >> Followup-For: Bug #812199 >> >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA256 >> >> Reassigned from 'openntpd' >> >> Since 'hwclock --systohc' no longer is run at reboot/shutdown, some NTP >> implementations fail at performing the initial synchronization because the >> delta between RTC and system time is to big. > > The only thing I can suggest is that you switch to a working NTP > implementation because normally hwclock would not be involved at > all in updating the RTC after NTP sync.
Nobody said that any NTP daemon would run hwclock. >> It also seems that something sets the system time to the wrong offset to >> UTC. Typically, after reboot, the system time is set to what would be UTC >> time rather than the expected correct local time. what would instead be >> expected is for system tiem to be an offset to UTC and for the RTC to be >> presumed to run at UTC time. > > Sounds bad but you leave me with nothing to go on so impossible to > do anything about.... moreinfo, unreproducible. Here's a question: why isn't the current system time saved to RTC upon reboot/shutdown anymore? Martin-Éric
