* 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