> This is all in the manpage, see man hwclock. If you use ntpd,
> you probably don't want hwclock to adjust, just set the time.
When the machine reboots from a power interruption Internet connection
may be unavailable (usual here). Ntpd can start synchronized to an RTC
but time is inaccurate because hwclock has not adjusted it. When
Internet connection reestablishes ntpd notices the time conflict and
terminates. Human intervention or cron lines can run ntpdate and then
restart ntpd. This results in time of low quality.
There are lots of high quality and cost hardware solutions. The
solution in my first post was a very small kernel patch to add an
11 minute update log so hwclock etc could adjust the time. Any
comments on my patch?
-- Regards, Ian Maclaine-cross (email@example.com) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/