Re: set_rtc_mmss: can't update from 0 to 59

[Russell King <rmk@arm.linux.org.uk>]

Paul Gortmaker writes:
> It smells like policy in the kernel to me.  What if a user wants to run NTP
> but wants the CMOS RTC time as an independent clock to do something else
> (possibly with the option of having a meaningful /etc/adjtime too) ?

NTP and adjtime are synomonous - NTP uses the adjtimex call to adjust the
local clock.  Therefore, when running NTP, leave adjtime well alone
(unless you want to break NTP).  You either use NTP or adjtime, not both.

> Can't the people who want the current behaviour simply have a crontab
> that runs (hw)clock -[u]w from util-linux at whatever interval they want?

And how do you handle the situation where NTP hasn't synchronised, and
therefore the local hardware clock should not be updated?  Sometimes
the hardware clock is higher precision than the kernels idea of time
(ok, not in cheap PCs).
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |         Russell King        rmk@arm.linux.org.uk      --- ---
  | | | | http://www.arm.linux.org.uk/personal/aboutme.html   /  /  |
  | +-+-+                                                     --- -+-
  /   |               THE developer of ARM Linux              |+| /|\
 /  | | |                                                     ---  |
    +-+-+ -------------------------------------------------  /\\\  |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/