Time problems

David david.maillists at gmail.com
Wed Jun 11 19:32:44 BST 2008

I *think* (but I am not sure) that the default init.d scripts write the
system time into the hardware clock when shutting down (it is what the
command hwclock --systohc does).

So I have the hardware clock to the *local time* and, whenever the system
clock changes (sync with time servers, manual adjustment of the clock, etc),
it will be written into the hardware clock during next shutdown (or you can
do it manually with hwclock --systohc).

But I am not sure at all, take the information at your own risk :-)

2008/6/11 Anne Wilson <cannewilson at googlemail.com>:

> On Wednesday 11 June 2008 18:32:48 David wrote:
> > hwclock --systohc
> No output is what I got :-)
> I might do better if I understood the relationship between the
> various 'clocks'.  For instance, I know that tzdata tells it when BST
> begins.
> Doesn't that need the BIOS clock to be UTC, so that it can act on it?
> I'd really appreciate some explanations :-)
> Anne
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde/attachments/20080611/496673c8/attachment.htm>
-------------- next part --------------
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

More information about the kde mailing list