Control: reassign -1 systemd Control: forcemerge 755722 -1 Hello Yoric Kotchukov.
On Wed, Aug 12, 2015 at 12:48:46AM +0600, Yoric Kotchukov wrote: > Hello. > > 09.08.2015, 20:44, "Andreas Henriksson" <[email protected]>: > > > $ systemctl cat hwclock > > # /dev/null > > This is my case. > > > If you're still running sysvinit, then /etc/init.d/hwclock.sh > > should invoke hwclock with the right set of arguments. > > I expected this behavior. I will think how to get out of the situation. > It's not clear to me if you're using systemd or not. Anyway, if you are using systemd then the hardware clock is handled a bit differently then in the old days. You can read lengthy posts about it on the interweb. Martin Pitt reminded me that systemd by design does *not* sync the hardware clock on system shutdown (in recent versions?). Things like ntpd will regularly sync the hardware clock when it knows it has a good system time to actually store. This issue has already been discussed in the past. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755722 Reassigning and merging this bug report with that one. Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
