Daniel Pocock <dan...@pocock.pro> writes: > However, at the time when I ran ntpdate, ntp was not running. I had > brought up the network manually due to an interface renaming issue on > the first boot. Maybe when somebody runs ntpdate in a scenario like > that the kernel is not sending the new date/time to the hardware clock.
Right, ntpdate for some reason doesn't set the flag to do this. > I had simply assumed that it would be persisted at shutdown but maybe > ntpdate could be patched to do whatever ntpd does to encourage the > kernel to persist it. sysvinit I believe used to always persist the clock to the hardware clock during shutdown. systemd doesn't do that, for reasons that I've not thought about in any depth. So that's a change, which is understandably surprising. If you get in the habit of using ntpd instead of ntpdate to do the one-time clock syncs, that might fix the problem (alas, I forget the set of command line flags that do the same thing as ntpdate). -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>