Op donderdag 7 december 2017 14:08:56 CET schreef Freek de Kruijf: > Op donderdag 7 december 2017 01:05:18 CET schreef Stefan Brüns: > > On Wednesday, December 6, 2017 11:58:16 PM CET Freek de Kruijf wrote: > > > Op woensdag 6 december 2017 15:58:38 CET schreef Brüns, Stefan: > > > > On Mittwoch, 6. Dezember 2017 15:23:19 CET Freek de Kruijf wrote: > > > > > In Raspbian I noticed a packet always included in the image called > > > > > fake- > > > > > hwclock. I used the tar.gz file together with a .spec file to > > > > > generate > > > > > this > > > > > packet for openSUSE distributions for systems without a Real Time > > > > > Clock. > > > > > > > > > > The description is: > > > > > Some machines don't have a working realtime clock (RTC) unit, or no > > > > > driver > > > > > for the hardware that does exist. > > > > > fake-hwclock is a simple set of scripts to save the kernel's current > > > > > clock > > > > > periodically (including at shutdown) and restore it at boot so that > > > > > the > > > > > system clock keeps at least close to realtime. This will stop some > > > > > of > > > > > the > > > > > problems that may be caused by a system believing it has travelled > > > > > in > > > > > time > > > > > back to 1970, such as needing to perform file system checks at every > > > > > boot. > > > > > > > > > > On top of this, use of NTP is still recommended to deal with the > > > > > fake > > > > > clock > > > > > "drifting" while the hardware is halted or rebooting. > > > > > > > > > > Hope this is accepted to be included. > > > > > > > > Does this offer anything beyond what systemd-timesyncd offers? > > > > > > Don't know. I would expect, if this does the same as this package, by > > > default to be included in images for systems without a Real Time Clock. > > > I > > > did not notice such a inclusion, but I struggled with dates Jan 1, 1970 > > > after starting a Raspberry Pi using openSUSE, before NTP finally set the > > > time proper. This packet sets the time very early in the boot process so > > > times are beyond times last used before the system went down, at least > > > after a proper shutdown. After a crash this time might be off less than > > > one > > > hour. > > > > systemctl-timesyncd is not enabled by default (probably it should on e.g. > > the RPi images). > > It definitely should. I made a bug report on it: > https://bugzilla.suse.com/show_bug.cgi?id=1071763
My latest test with this service on a Rasberry Pi 3B, with tha latest aarch64 image, shows that it is not working. After a reboot the journal always starts with date/times Oct 26 14:29:36 and only after NTP becomes active, which is after the network is active, the date/time becomes the current time. For now fake-hwclock does a better job. -- fr.gr. Freek de Kruijf member openSUSE -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
