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