On Fri, Jul 25, 2003 at 11:54:19AM +0300, Amichai Rotman wrote: > Hi Clan, > > I have a weird problem: My system time drifts 18 minutes back. I set the right > time and after a while (I can't say how long) it goes back 15-18 minutes... > > i.e. now: > > my KDE Clock applet reads 11:29 > Aruzei Zahav Digital clock reads 11:47 > output from hwclock reads 11:47 > > Which means the problem lies with the KDE applet....
Not as far as I see it - the problem is with the system time (`date`). What does it say? As far as I know, hwclock is relevant for boot and shutdown times (it is read to the system clock at boot and saved back at shutdown), it's not supposed to be used anywere else. 1. Does your system read the hwclock at boot time (I think it's standard, at least with Debian, but check your system). 2. What if you do "hwclock --hctosys", does the system keep the time after that? 3. Can you setup an NTP daemon on that system? It should handle drifting clocks after a couple of days of running. (run "ntpdate server1 server2 server3" immidietly before running the ntp daemon itself). > > I have tried to change time with hwclock and right-clicking the applet > (through KDE) It's a 99.99% chance the applet reads the system time, not the harware clock time. (the other 0.01% is just because I haven't actually looked at the source). > > Both hwclock and the KDE applet settings show IDT as timezone and KDE has > Asia/Jerusalem set as area. Where does hwclock tells the timezone? Mine looks like this: # hwclock -r Fri Jul 25 21:39:21 2003 -0.913389 seconds And also: % hwclock --version hwclock from util-linux-2.11z HTH, --Amos ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
