Re: Time problems

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

 



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@xxxxxxxxxxxxxx>:
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


___________________________________________________
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.

[Index of Archives]     [Trinity (TDE) Desktop Users]     [Fedora KDE]     [Fedora Desktop]     [Linux Kernel]     [Gimp]     [GIMP for Windows]     [Gnome]     [Yosemite Hiking]
  Powered by Linux