[opensuse] my clock keep changing
my opensuse 10.2's clock keep changing everytime i reboot. Usually everytime i reboot, the clock will be about 30 minutes behind from the previous time setting, and if i reboot two, it will 60 mniutes behind and so on. I have to change it manully. How do i fix it? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 15 August 2007, Hans Linux wrote:
my opensuse 10.2's clock keep changing everytime i reboot. Usually everytime i reboot, the clock will be about 30 minutes behind from the previous time setting, and if i reboot two, it will 60 mniutes behind and so on. I have to change it manully. How do i fix it?
--------------- I believe I experienced this once when I had set the clock to "local" rather than UTC. Lee -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 15 August 2007 21:35, BandiPat wrote:
On Wednesday 15 August 2007, Hans Linux wrote:
my opensuse 10.2's clock keep changing everytime i reboot. Usually everytime i reboot, the clock will be about 30 minutes behind from the previous time setting, and if i reboot two, it will 60 mniutes behind and so on. I have to change it manully. How do i fix it?
---------------
I believe I experienced this once when I had set the clock to "local" rather than UTC.
Lee
And cure is usually to set correct time, delete file adjtime and reboot. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Rajko M. wrote:
On Wednesday 15 August 2007 21:35, BandiPat wrote:
On Wednesday 15 August 2007, Hans Linux wrote:
my opensuse 10.2's clock keep changing everytime i reboot. Usually everytime i reboot, the clock will be about 30 minutes behind from the previous time setting, and if i reboot two, it will 60 mniutes behind and so on. I have to change it manully. How do i fix it?
I believe I experienced this once when I had set the clock to "local" rather than UTC.
Lee
And cure is usually to set correct time, delete file adjtime and reboot.
No reboot needed, since this is fortunately not microsoft windoze. Substitute "restart ntpd" in place of "reboot". Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 15 August 2007 22:25, joe wrote:
Rajko M. wrote:
On Wednesday 15 August 2007 21:35, BandiPat wrote:
On Wednesday 15 August 2007, Hans Linux wrote:
my opensuse 10.2's clock keep changing everytime i reboot. Usually everytime i reboot, the clock will be about 30 minutes behind from the previous time setting, and if i reboot two, it will 60 mniutes behind and so on. I have to change it manully. How do i fix it?
---------------
I believe I experienced this once when I had set the clock to "local" rather than UTC.
Lee
And cure is usually to set correct time, delete file adjtime and reboot.
No reboot needed, since this is fortunately not microsoft windoze. Substitute "restart ntpd" in place of "reboot".
Hi Joe, Reboot is not taboo. It is one of the ways to have system time set. Easy to write and easy to run. I guess that running /etc/init.d/boot.clock restart with properly set environment variables will do the same, but it is much more to write, read and type. For me to avoid advice to reboot, I would have to look: man hwclock man date script /etc/init.d/boot.clock and then extract information in usable form. After some hour(s) of reading and testing (create test case) that advice will really work I would be ready to avoid reboot that takes few seconds to type in mail and 2-3 minutes to perform. Does that make any sense? -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Rajko M. wrote:
On Wednesday 15 August 2007 22:25, joe wrote:
Rajko M. wrote:
On Wednesday 15 August 2007 21:35, BandiPat wrote:
On Wednesday 15 August 2007, Hans Linux wrote:
my opensuse 10.2's clock keep changing everytime i reboot. Usually everytime i reboot, the clock will be about 30 minutes behind from the previous time setting, and if i reboot two, it will 60 mniutes behind and so on. I have to change it manully. How do i fix it?
I believe I experienced this once when I had set the clock to "local" rather than UTC.
Lee And cure is usually to set correct time, delete file adjtime and reboot. No reboot needed, since this is fortunately not microsoft windoze. Substitute "restart ntpd" in place of "reboot".
Hi Joe,
Reboot is not taboo. It is one of the ways to have system time set. Easy to write and easy to run.
I guess that running /etc/init.d/boot.clock restart with properly set environment variables will do the same, but it is much more to write, read and type.
For me to avoid advice to reboot, I would have to look: man hwclock man date script /etc/init.d/boot.clock and then extract information in usable form. After some hour(s) of reading and testing (create test case) that advice will really work I would be ready to avoid reboot that takes few seconds to type in mail and 2-3 minutes to perform. Does that make any sense?
I suppose it does, but it sounds contrived - normally I would just type: rcntpd restart and in the worst case, I might also type: hwclock --systohc True, rebooting isn't taboo, but it leaves a bad taste for unix people. People coming from a microsoft background they tend to reboot for every little thing, so I try to encourage them to sit on their hands instead, so they can gain the realization that they don't *have* to reboot for every little thing like they did in the bad old microsoft days. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2007-08-15 at 21:32 -0700, joe wrote:
I suppose it does, but it sounds contrived - normally I would just type:
rcntpd restart
Which will not work at all if he is not using ntpd. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGxJm+tTMYHG2NR9URAqRKAJ4ifnqmI91ebii1qeoFgVWUqCD75wCcCGiI Lip/tz19uF79YLDLp4RbP+M= =SuVi -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
The Wednesday 2007-08-15 at 21:32 -0700, joe wrote:
I suppose it does, but it sounds contrived - normally I would just type:
rcntpd restart
Which will not work at all if he is not using ntpd.
IIUC the discussion concerned how to best restart ntpd. The OP was concerned about the accuracy of time on his linux system, and ntpd (or periodic ntpdate) is the obvious answer. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2007-08-16 at 11:48 -0700, Sloan wrote:
rcntpd restart
Which will not work at all if he is not using ntpd. IIUC the discussion concerned how to best restart ntpd. The OP was concerned about the accuracy of time on his linux system, and ntpd (or periodic ntpdate) is the obvious answer.
No, it isn't. Not if he has a missaligned "/etc/adjtime", as he surely has, and that is not solved by restarting ntpd a hundred times. Everytime he boots up the time would be bad again. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGxKsZtTMYHG2NR9URAijhAJ92Y1YuQ+HTJ8QA3g5nwHuVdYwKWQCcCHUK C18BQ6WoGJRKxKcbrrQV/80= =FKXH -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
The Thursday 2007-08-16 at 11:48 -0700, Sloan wrote:
rcntpd restart Which will not work at all if he is not using ntpd. IIUC the discussion concerned how to best restart ntpd. The OP was concerned about the accuracy of time on his linux system, and ntpd (or periodic ntpdate) is the obvious answer.
No, it isn't. Not if he has a missaligned "/etc/adjtime", as he surely has, and that is not solved by restarting ntpd a hundred times. Everytime he boots up the time would be bad again.
I've not seen that condition in 10 years among the few hundred linux boxes here, but should /etc/adjtime actually be defective, one could just nuke it and be good to go. I'd be more concerned with the root cause, i.e. how did /etc/adjtime get corrupted in the first place. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 16 August 2007 16:16, Sloan wrote:
Carlos E. R. wrote:
The Thursday 2007-08-16 at 11:48 -0700, Sloan wrote:
rcntpd restart
Which will not work at all if he is not using ntpd.
IIUC the discussion concerned how to best restart ntpd. The OP was concerned about the accuracy of time on his linux system, and ntpd (or periodic ntpdate) is the obvious answer.
No, it isn't. Not if he has a missaligned "/etc/adjtime", as he surely has, and that is not solved by restarting ntpd a hundred times. Everytime he boots up the time would be bad again.
I've not seen that condition in 10 years among the few hundred linux boxes here, but should /etc/adjtime actually be defective, one could just nuke it and be good to go. I'd be more concerned with the root cause, i.e. how did /etc/adjtime get corrupted in the first place.
Hi Joe, that was problem occasionally after some kernel updates that triggered avalanche of complains on shifting clock. I had that 2 times, and above procedure helped every time. If it doesn't help than we can go and figure out what was the root cause. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2007-08-16 at 14:16 -0700, Sloan wrote:
Carlos E. R. wrote:
The Thursday 2007-08-16 at 11:48 -0700, Sloan wrote:
rcntpd restart Which will not work at all if he is not using ntpd. IIUC the discussion concerned how to best restart ntpd. The OP was concerned about the accuracy of time on his linux system, and ntpd (or periodic ntpdate) is the obvious answer.
No, it isn't. Not if he has a missaligned "/etc/adjtime", as he surely has, and that is not solved by restarting ntpd a hundred times. Everytime he boots up the time would be bad again.
I've not seen that condition in 10 years among the few hundred linux boxes here, but should /etc/adjtime actually be defective, one could just nuke it and be good to go. I'd be more concerned with the root cause, i.e. how did /etc/adjtime get corrupted in the first place.
Then you haven't been reading the list during the past ten years, because the condition has been reported here several times :-P Go ahead, search the archive: how /etc/adjtime becomes missaligned or defective on a SuSE system has been explained here several times. It is documented, too. Also, remember that there are many PCs out there without a permanent network connection, for which running ntpd is not an option. Nevertheless, keeping the clock reasonable accurate is possible. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGxez/tTMYHG2NR9URAtKOAJ91cdJJR/2aHY7X1pp8b1oMj+4TsgCgjPmw 6Jr81BB9E74ngvoqAP3pc60= =0uqb -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 15 August 2007 22:25, joe wrote:
Rajko M. wrote:
On Wednesday 15 August 2007 21:35, BandiPat wrote:
On Wednesday 15 August 2007, Hans Linux wrote:
my opensuse 10.2's clock keep changing everytime i reboot. Usually everytime i reboot, the clock will be about 30 minutes behind from the previous time setting, and if i reboot two, it will 60 mniutes behind and so on. I have to change it manully. How do i fix it?
---------------
I believe I experienced this once when I had set the clock to "local" rather than UTC.
Lee
And cure is usually to set correct time, delete file adjtime and reboot.
No reboot needed, since this is fortunately not microsoft windoze. Substitute "restart ntpd" in place of "reboot".
Joe
Please explain how you plan to check if the clock changes on booting with out rebooting the computer. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
SOTL wrote:
On Wednesday 15 August 2007 22:25, joe wrote:
Rajko M. wrote:
On Wednesday 15 August 2007 21:35, BandiPat wrote:
On Wednesday 15 August 2007, Hans Linux wrote:
my opensuse 10.2's clock keep changing everytime i reboot. Usually everytime i reboot, the clock will be about 30 minutes behind from the previous time setting, and if i reboot two, it will 60 mniutes behind and so on. I have to change it manully. How do i fix it?
I believe I experienced this once when I had set the clock to "local" rather than UTC.
Lee And cure is usually to set correct time, delete file adjtime and reboot. No reboot needed, since this is fortunately not microsoft windoze. Substitute "restart ntpd" in place of "reboot".
Joe
Please explain how you plan to check if the clock changes on booting with out rebooting the computer.
If your ntpd config is right, the time will be right. My answer was about the fix, but if you like rebooting and are naturally curious, feel free, go ahead. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2007-08-16 at 20:00 -0700, joe wrote:
SOTL wrote:
And cure is usually to set correct time, delete file adjtime and reboot. No reboot needed, since this is fortunately not microsoft windoze. Substitute "restart ntpd" in place of "reboot".
Please explain how you plan to check if the clock changes on booting with out rebooting the computer.
:-)
If your ntpd config is right, the time will be right.
Nope.
My answer was about the fix, but if you like rebooting and are naturally curious, feel free, go ahead.
Hint: examine the boot scripts to determine how the system clock is setup during bootup. There are two places. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGxeuStTMYHG2NR9URAk9KAJsEHwSOI9pWeWm3QFgep2V1JOv6PwCeIHmo swcdl1bOYQlHXUy+olvNztM= =EJYn -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Rajko M. wrote:
On Wednesday 15 August 2007 21:35, BandiPat wrote:
On Wednesday 15 August 2007, Hans Linux wrote:
my opensuse 10.2's clock keep changing everytime i reboot. Usually everytime i reboot, the clock will be about 30 minutes behind from the previous time setting, and if i reboot two, it will 60 mniutes behind and so on. I have to change it manully. How do i fix it?
I believe I experienced this once when I had set the clock to "local" rather than UTC.
Lee
And cure is usually to set correct time, delete file adjtime and reboot.
This may be a stupid question. When was the cmos battery replaced last? -- Billie Walsh The three best words in the English Language: "I LOVE YOU" Pass them on! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
The usual method of handling that is to simply run ntpd - manual adjustment of such things should not be required in the linux world. Joe Hans Linux wrote:
my opensuse 10.2's clock keep changing everytime i reboot. Usually everytime i reboot, the clock will be about 30 minutes behind from the previous time setting, and if i reboot two, it will 60 mniutes behind and so on. I have to change it manully. How do i fix it? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2007-08-16 at 09:25 +0700, Hans Linux wrote:
my opensuse 10.2's clock keep changing everytime i reboot. Usually everytime i reboot, the clock will be about 30 minutes behind from the previous time setting, and if i reboot two, it will 60 mniutes behind and so on. I have to change it manully. How do i fix it?
Known problem. Procedure: - stop ntpd if you are using it (and restart at the end if so) - Change time manually. - Verify as root in an xterm using "date". Ensure that the time zone is correct; otherwise, correct using Yast. - Issue "hwclock --systohc --localtime" or ""hwclock --systohc --utc" as appropiate (you should know wheter your bios keeps utc or localtime; if in doubt, check /etc/sysconfig/clock - HWCLOCK). - Delete /etc/adjtime Reboot or halt your computer when you need to; next time the time should be correct. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGxJwUtTMYHG2NR9URAj9NAJ9l03MUy7TT4WSI3l/PCGY9xer3ZQCfXo34 puDGLoBtrF1f/AL+6oi2peY= =XxHo -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (8)
-
BandiPat -
Billie Walsh -
Carlos E. R. -
Hans Linux -
joe -
Rajko M. -
Sloan
-
SOTL