Note: Even with the change in /etc/rc.conf recently, the HARDWARECLOCK= line still works.
]]>The solution for me was to change /etc/rc.conf and set
HARDWARECLOCK="virtual"
(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.
]]>/offtopic, but if you have a long uptime, its interesting to watch the clocks drift apart...
]]>https://wiki.archlinux.org/index.php/Sy … caltime.3F
There was a detailed discussion at arch-general mailing list about this, those interested can take a look here:
]]>I've tried it and seems to be working fine, so no need for localtime then I guess.
]]>"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?
Thanks.
]]>