On Wednesday 13 April 2011 08.05:23 Andrew O. Shadoura wrote:
> ii) Possibly, `hwclock.sh stop` should be run more frequently than just
> once on shutdown, because it sometimes happens that the system doesn't
> shut down correctly. If that happens after some time correction (like
> DST), system tim
On Wed, 13 Apr 2011 09:05:23 +0300, "Andrew O. Shadoura"
wrote:
> Hello,
>
> I'd like to hear opinions on hwclock.sh operation.
>
> Few thoughts of my own:
>
> i) It's still quite common that battery in the RTC becomes flat.
> In this case, hwclock.sh silently sets system clock to 1970 (or
> w
"Andrew O. Shadoura" writes:
> iii) Also, it would be good to hear opinions about negative
> consequences of saving the system time to the RTC on frequent basis.
My openmoko does a suspend/resume cycle every 10 minutes. RTC time can
only be set at one second granularity. If I write to RTC on ever
Hello,
I'd like to hear opinions on hwclock.sh operation.
Few thoughts of my own:
i) It's still quite common that battery in the RTC becomes flat.
In this case, hwclock.sh silently sets system clock to 1970 (or
whatever else nonsense), efficiently turning file access and modify
times into a mess
4 matches
Mail list logo