Re: mimic the RTC restart delay (was: hwclock issue)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 17 Jun 2008 12:00:41 +0200 (CEST)
Alain Guibert <alguibert+ulng@xxxxxxx> wrote:

> The last --systohc was yesterday night at shutdown. Now 10 hours later,
> the RTC has accumulated nearly 5 seconds of drift. But hwclock --hctosys
> compensates its biggest part, and is in error by only 12 milliseconds.
> There half a second of error would be an issue.

 It' surely an issue, but it depends on what are you doing
 with that clock...?
 
 Launching nuclear missiles? :-D

 If not, you can always use ntpdate/ntp to correct the time.

 Eventually one can have an option to tell hwclock how many msec
 to compensate.

-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Torino, Italy

  http://www.towertech.it

--
To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux