"Robert Rozman" wrote Fri Apr 30 2004 - 13:35:53 CEST: (Top posting switched to bottom post) (I left this as a long mail, because of break April to May)
----- Original Message ----- From: <GarUlbricht7> Sent: Saturday, April 17, 2004 12:08 AM Subject: RE: [SLE] realtime clock probs
< http://lists.suse.com/archive/suse-linux-e/2004-Apr/1297.html >
John Sowden wrote:
in Suse 8.0, I have noticed that the time gets off by months, even once by years. I can fix it in ms-dos (dual boot) and it works fine.
now i notice on booting that linux hangs on the real time clock entry for about a minute before it continues, no warning message, etc. thoughts?
Hi John,
I am running dual boot also.
What I do is go into M$ and roughhly adjust the time using their control system. (I had to do it for daylight savings time.)
***** I adjust it to nearest 10 seonds or so..******
Then I go back into Linux, and open up a link to an offiical time site (eg: http://www.time.gov/ )
and then set the time off the command line as root, eg:
"date --set 14:55:25"
the above will set the system time to 14:55:25; then I do:
"hwclock --systohc"
so that system time is copied to the cmos chip;
and then do:
"rm /etc/adjtime" (all w/o quotes)
so time adjusting scripts don't think that the clock was slow or fast, and **the scripts** repeat the adjustment automatically on boot.
This question is often asked. See for a longer explaination Carlos' post:
http://lists.suse.com/archive/suse-linux-e/2003-Nov/0001.html
Hope this helps, Gar --
Hi,
I'm too having problems with suse time setting going sometimes way foo (6 hours is last record).
What do you mean to repeat adjustment at boot. Should I run
"hwclock --systohc"
and remove /etc/adjtime on every boot ?
Thanks, Robert.
Hi Robert, The simple answer is if your battery is fresh (not old) the machine should keep good time and you don't need to follow the above procedure on every boot. You just need to do it once. This procedure is based on an earlier posting of Carlos. In the above post because John is running dual boot, I was suggested he set the time in his Microsoft OS first. (Most M$ boxes are run on local time.) Microsoft uses a different system for keeping time than Linux does. So if you have a dual boot, it is best if you get the MS side to nearest minute or two, you can then boot your SuSE OS, and on Linux I try to get the time right to the nearest second. What I do is open up a Konq window on an official time site, and the open up a shell (as root) on top of the Konq window. I set the time on the CL 5 to 10 second ahead, and then enter it as the time gets in the Konq window to what I wrote. Hopefully that makes sense. I am adjusting the time off the command line, rather than using YaST and that has worked better for me. YMMV. The procedure is (as outlined above), do:
"date --set 14:55:25"
the above will set the system time to 14:55:25; then I do in the shell:
"hwclock --systohc"
so that system time is copied to the cmos chip;
and then do also in the shell:
"rm /etc/adjtime" (all w/o quotes)
Then I log out of the shell by doing either "exit", or "Ctrl+d". At that point the time should be OK for next several months, even if I reboot fairly frequesntly and go between MS and Linux. As I said above you don't have to keep doing it, but if you don't do the above steps, MS time scripts fight with Linux scripts, and if you don't "rm /etc/adjtime" the system thinks that it has a problem and tries to correct when it shouldn't. Hope this explaination makes it clear as to what to do. If not, ask again, and/or read "man hwclock" Friendly greetings, -- __________________________________________________________________ Introducing the New Netscape Internet Service. Only $9.95 a month -- Sign up today at http://isp.netscape.com/register Netscape. Just the Net You Need. New! Netscape Toolbar for Internet Explorer Search from anywhere on the Web and block those annoying pop-ups. Download now at http://channels.netscape.com/ns/search/install.jsp