Jon Clausen wrote:
On Wednesday 04 April 2001 03:46, you wrote:
Since upgrading from 7.0 to 7.1 my system never seems to be able to set the time properly. It's fine in the BIOS, and worked perfectly with 7.0/2.2.16, but now with 7.1/2.2.18 it's always hours off. I've tried every combination via yast1 I can think of (e.g. "America/Los Angeles", PST, PDT, GMT-8, all tried with BIOS uses "Local Time" or "GMT") and it is /still/ off by 4-8hours depending on which combo I try.
Me too! (Only two hours but still)
This subject was dealt with some time ago on the list. Unfortunately I didn't pay much attention to it at the time (I was stil using 6.4 then). But I seem to remember some solution being presented (?)
Does anyone still have it laying around in their mail?
It read like a genuine fix, not a workaround...
hwclock or something?
You may be referring to the fact that if you change the system time (i.e. do a 'date 040409052001.00') then this isn't reflected in a change in the system's hardware clock. Hence, when you reboot, you are back to using the old time. To set the hardware clock to the current system time, use the command: hwclock --utc --systohc if your hardware clock stores time in UTC (recommended) or this command: hwclock --systohc if your hardware clock stores time in local time. So, try setting your time to the correct time and then running one of the above commands. I'm not sure if this is the solution to the original problem though... Hope that helps, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\