Hi, in the new initscripts update announcement there's the following sentence:
"We now strongly discourage the use of HWCLOCK="localtime", as this may lead to several known and unfixable bugs. However, there are no plans to drop support for "localtime"."
I'm dual booting my machine with a Windows OS, so I've always had it set to localtime; otherwise Windows would display the time incorrectly. What are the known and unfixable bugs when set to "localtime"? Is it anyway I could put it UTC and keep Windows working as usual? What do you (dual booting users) do?
you can set your windows machine to use UTC too.
Arch64/DWM || My Dropbox referral link
Thanks JokerBoy, I wasnt aware of that trick.
Proud Arch Linux user since 2007.
Thank you for the tip! I didn't know that either.
I've tried it and seems to be working fine, so no need for localtime then I guess.
For the problems caused by use of localtime, take a look here:
There was a detailed discussion at arch-general mailing list about this, those interested can take a look here:
I wouldn't have a problem setting my hwclock to utc if it wasn't for the fact that my laptop has an external lcd clock that displays the hwclock time.... which i would prefer to use, and in localtime
/offtopic, but if you have a long uptime, its interesting to watch the clocks drift apart...
Any society that would give up a little liberty to gain a little security will deserve neither and lose both.
The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man.
-George Bernard Shaw
Last edited by Doctor Drive (2011-06-07 09:33:57)
I have a company laptop where the time is set automatically whenever it connects to the domain. (windows)
The IT staff is rather large with me doing stuff on my own, but I didn't want to change anything in the main system.
The solution for me was to change /etc/rc.conf and set
(I guess any value other than "localtime" and "utc" would do the trick)
Then I added the following to /etc/rc.local
hwclock -s --localtime
That way my Linux system never changes the hardware clock. It only reads it on every boot.
MadEye | Registered Linux user #167944 since 2000-02-28 | Homepage
@madeye That is a fantastic solution for those who use Windows most of the time (especially Windows XP or Vista, but also 7) and Arch only some of the time. Thanks.
Note: Even with the change in /etc/rc.conf recently, the HARDWARECLOCK= line still works.