[Bug 563618] Re: Ignoring a broken clock results in infinite reboots; not ignoring results in fsck failure; no solution to this problem

[Jamie Bennett]

@davem

Of course writing at shutdown/reboot only works on a clean shutdown, not
on a loss of power. Writing the clock value on _boot-up_ maybe wiser,
yes your clock will be out by boot time+uptime but at least it will be a
sane value for next time and as you mentioned, with network connectivity
you can retrieve the correct time via ntp.

-- 
Ignoring a broken clock results in infinite reboots; not ignoring results in fsck failure; no solution to this problem
https://bugs.launchpad.net/bugs/563618
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to util-linux in ubuntu.