![](https://seccdn.libravatar.org/avatar/d70f8a8240c69007852b9d1bf27e170b.jpg?s=120&d=mm&r=g)
Patrick, Did you notice that the trailer on each message on suse-kde says not to crosspost? * Patrick (tracerb@sprintmail.com) [020509 17:03]:
Anthony brought up the subject of time/date being wrong on his mails, but my problem is somewhat different. This seems to be a problem that goes back to the 7.1 days! Each time I boot up, the system clock has the wrong time and requires resetting. The bios clock is correct as I have checked that already.
This sounds vaguely familiar...
Going back to a previous mail when the problem showed up back in October 2001, it seems to be a bug in the /etc/rc.d/boot script which will cause the system clock to NOT be set to the hardware clock on boot. The bug has been around for quite some time it seems. The problem was simple in that adding the full path to the hwclock command solved the problem. The solution was to change the CLOCKCMD=hwclock in /etc/rc.d/boot file to CLOCKCMD=/sbin/hwclock and for good measure also adding /sbin/hwclock --hctosys in the /etc/rc.d/boot.local file!
Ah ha! I don't know where you guys are digging this stuff up at but here's my response the last time someone posted this: http://lists.suse.com/archive/suse-linux-e/2002-Mar/0390.html -- -ckm
![](https://seccdn.libravatar.org/avatar/f4512fd533cb9bd5cdca790c6b819d81.jpg?s=120&d=mm&r=g)
On Thursday 09 May 2002 20:11, Christopher Mahmood wrote:
Ah ha! I don't know where you guys are digging this stuff up at but here's my response the last time someone posted this: http://lists.suse.com/archive/suse-linux-e/2002-Mar/0390.html
Oh, yes, thanks Chris, that was the same article I already had, but it doesn't help much with SuSE 8.0, things are way different! I did find the solution though and it turned out to be that I had setup my timezone wrong. It was actually changing my hardware clock time each and every boot, so neither clock was right! Change the Time Zone to local and my correct area and everything seems to be right again. :o) Patrick -- --- KMail v1.4 --- SuSE Linux Pro v8.0 --- Registered Linux User #225206 Magic Page Products -- Amiga-SuSE-PC Sales & Service URL: http://home.sprintmail.com/~tracerb
![](https://seccdn.libravatar.org/avatar/eba995a98a959e1d4ae7b36a1ca31293.jpg?s=120&d=mm&r=g)
On Friday 10 May 2002 02:11, Christopher Mahmood wrote:
Patrick,
Did you notice that the trailer on each message on suse-kde says not to crosspost?
* Patrick (tracerb@sprintmail.com) [020509 17:03]:
Anthony brought up the subject of time/date being wrong on his mails, but my problem is somewhat different. This seems to be a problem that goes back to the 7.1 days! Each time I boot up, the system clock has the wrong time and requires resetting. The bios clock is correct as I have checked that already.
This sounds vaguely familiar...
Going back to a previous mail when the problem showed up back in October 2001, it seems to be a bug in the /etc/rc.d/boot script which will cause the system clock to NOT be set to the hardware clock on boot. The bug has been around for quite some time it seems. The problem was simple in that adding the full path to the hwclock command solved the problem. The solution was to change the CLOCKCMD=hwclock in /etc/rc.d/boot file to CLOCKCMD=/sbin/hwclock and for good measure also adding /sbin/hwclock --hctosys in the /etc/rc.d/boot.local file!
Ah ha! I don't know where you guys are digging this stuff up at but here's my response the last time someone posted this: http://lists.suse.com/archive/suse-linux-e/2002-Mar/0390.html
Hmm... is this related to the following bug: occasionally the timezone from the kicker clock changes to a random value (perhaps time changes too), but only in KDE(!) Killing kicker and restarting it with "kdeinit kicker &" solved the symptom. I've suspected xntpd to be the cause of the bug (without proof). 1. This seems SuSE specific (KDE-2.x) 2. The bug seems to be solved (I recall at least 1 occurrence in KDE-3.0, but I think it was before I've updated my system to the latest packages. Cristopher, I'm curious about your opinion on this :-) Leen
![](https://seccdn.libravatar.org/avatar/d70f8a8240c69007852b9d1bf27e170b.jpg?s=120&d=mm&r=g)
* Leendert Meyer (leen.meyer@home.nl) [020510 11:47]:
1. This seems SuSE specific (KDE-2.x)
2. The bug seems to be solved (I recall at least 1 occurrence in KDE-3.0, but I think it was before I've updated my system to the latest packages.
Cristopher, I'm curious about your opinion on this :-)
Sorry, I have no idea what 'kicker' is and have never really used KDE so I'm not going to be much help with this. There doesn't seem to be a man or info page for kicker either...oh my. If kicker is something that changes the kernel time and you are running an ntp client then I don't doubt you'll have lots of time problems since /etc/ntp.drift is going to contain garbage. If you don't need to dual-boot another OS set your hardware clock to GMT, make sure to tell Linux that (/etc/sysconfig/clock:GMT="-u", /sbin/SuSEconfig --quick), and run xntpd making sure to set both /etc/sysconfig/xntp:XNTPD_INITIAL_NTPDATE="ip_of_timeserver" and (people often forget this part) /etc/ntp.conf:'server ip_of_timeserver'. When you are in /etc/ntp.conf you may also want to add 'restrict default ignore' to keep others from changing your clock remotely. If you do have to dual boot, set the hardware clock to localtime and /etc/sysconfig/clock:GMT="--localtime". The ntp configuration will be identical. If you are using a public timeserver use hostnames instead of IPs and add them /etc/hosts. Hope it helps, -- -ckm
![](https://seccdn.libravatar.org/avatar/eba995a98a959e1d4ae7b36a1ca31293.jpg?s=120&d=mm&r=g)
On Friday 10 May 2002 21:16, Christopher Mahmood wrote:
* Leendert Meyer (leen.meyer@home.nl) [020510 11:47]:
1. This seems SuSE specific (KDE-2.x)
2. The bug seems to be solved (I recall at least 1 occurrence in KDE-3.0, but I think it was before I've updated my system to the latest packages.
Cristopher, I'm curious about your opinion on this :-)
Sorry, I have no idea what 'kicker' is and have never really used KDE so I'm not going to be much help with this. There doesn't seem to be a man or info page for kicker either...oh my.
Ah, my fault to assume you knew KDE ;-). Kicker is the taskbar and can have (amongst other widgets) a clock applet running. It's a pity you don't know KDE, because KDE's clock changed sometimes, while the kernel clock was ok. BTW, I'm running SuSE Linux 7.3
If kicker is something that changes the kernel time and you are running an ntp client then I don't doubt you'll have lots of time problems since /etc/ntp.drift is going to contain garbage. If you
The clock applet in kicker is AFAIK passive, i.e. it only shows time, and doesn't change it. However the time can be changed _by_the_user_ in KDE's Control Center.
don't need to dual-boot another OS set your hardware clock to GMT, make sure to tell Linux that (/etc/sysconfig/clock:GMT="-u",
Yup, had that already
/sbin/SuSEconfig --quick), and run xntpd making sure to set both /etc/sysconfig/xntp:XNTPD_INITIAL_NTPDATE="ip_of_timeserver" and
filled with 4 ip#'s
(people often forget this part) /etc/ntp.conf:'server ip_of_timeserver'. When you are in /etc/ntp.conf you may also want
have the same 4 public servers there (ip#)
to add 'restrict default ignore' to keep others from changing your clock remotely.
added, thanks
If you do have to dual boot, set the hardware clock to localtime and /etc/sysconfig/clock:GMT="--localtime". The ntp configuration will be identical. If you are using a public timeserver use hostnames instead of IPs and add them /etc/hosts.
Hmm, hostnames instead of ip#, why is that? I don't see the benefit of that. The hostnames could (at some point in time) get different ip#, but those are fixed in /etc/hosts. I would have to change that file. Regards, Leen
![](https://seccdn.libravatar.org/avatar/9ef3b64d62b3842345b05c65c62726cd.jpg?s=120&d=mm&r=g)
On Friday 10 May 2002 10:22 pm, Leendert Meyer wrote:
The clock applet in kicker is AFAIK passive, i.e. it only shows time, and doesn't change it. However the time can be changed _by_the_user_ in KDE's Control Center.
Actually right clicking on the clock applet will offer you a number of options including changing the time, the time format and the type of clock. It's similar to the ms version in that respect. A problem I had was that regardless of where I changed the time, whenever the system was rebooted it was off by an hour. I set it up according to the time zone in which I live. I finally researched the issue and found that in a Linux only box (which this one is) you will achieve best results by using UMT time and not specifying a time zone. If you use a dual-boot box than the other OS usually sets the h/w clock. I changed settings in both yast2 and kde and have had good results. Ken
![](https://seccdn.libravatar.org/avatar/d70f8a8240c69007852b9d1bf27e170b.jpg?s=120&d=mm&r=g)
* Leendert Meyer (leen.meyer@home.nl) [020510 16:09]:
Ah, my fault to assume you knew KDE ;-).
A safe assumption, this is suse-kde afterall.
The clock applet in kicker is AFAIK passive, i.e. it only shows time, and doesn't change it. However the time can be changed _by_the_user_ in KDE's Control Center.
Hmmm...sounds complicated.
Hmm, hostnames instead of ip#, why is that? I don't see the benefit of that. The hostnames could (at some point in time) get different ip#, but those are fixed in /etc/hosts. I would have to change that file.
The idea is that you don't want to risk a DNS timeout at boot and not get the time set correctly before other services started. For example, I was once working on a customers mailserver and he had the xntp init script running last, after sendmail, named, etc. The hwclock turned out to several days ahead of reality. So the system starts to boot, sendmail starts and notices that it has all of this old undelievered mail sitting in the queue and decides that it's time to bounce all of it as undelieverable. Afterall, it was sitting in the queue for 4 days. But yes, the PTR records might change at some point. That's why I specified public timeservers. If you are in charge you'll know that you'll break a lot of stuff if you do change them. -- -ckm
![](https://seccdn.libravatar.org/avatar/7ce72c46b6ab41ad3bb822a75c7ea410.jpg?s=120&d=mm&r=g)
* Christopher Mahmood (ckm@suse.com) [020510 12:27]: :: ::Sorry, I have no idea what 'kicker' is and have never really used ::KDE so I'm not going to be much help with this. There doesn't seem ::to be a man or info page for kicker either...oh my. :: The kicker is what use to be called the kpanel. It's that Windowsish bar at the bottom with the big K that you can launch programs from. In my experience if you have xntpd running KDE should take it's tip from it...no matter what the user has set in his bios. :) -=Ben --=====-----=====-- mailto:ben@whack.org --=====-- If it's true that our species is alone in the universe, then I'd have to say that the universe aimed rather low and settled for very little. -GC --=====-----=====--
participants (5)
-
Ben Rosenberg
-
Christopher Mahmood
-
Ken Phelan
-
Leendert Meyer
-
Patrick