I have this problem too, but noticed that there's a difference between system time (as measured by "date") and hardware time (as measured by "hwclock"). Since the hardware clock seemed to keep up, while the system time sometimes lagged as much as 25% compared to real time, my solution was to make a cronjob which syncs system time with hardware time once an hour, thus making NTPd unneccessary.
I have attached the perlscript doing the syncing in case anyone's interested. (There is probably a better and "standard" way of doing this though, I find it surprising that the kernel or something doesn't do this automatically) // Joel On Thu, 3 Jul 2003, Christopher Egner wrote: > Alright, perhaps I'm a bit lost on this. My clock always runs off about > 20 to 30 minutes after a day or so. Only in linux though. I figured I'd > start using ntpd. However, I can't seem to figure out how to configure a > timezone for it. Any help here would be great. > -- > Christopher > > In 1968 it took the computing power of 2 C-64's to fly a rocket to the > moon. Now, in 1998 it takes the Power of a Pentium 200 to run Microsoft > Windows 95. Something must have gone wrong. > > > -- > [EMAIL PROTECTED] mailing list > >
#!/usr/bin/perl $date = `date`; $hw = `hwclock`; chop($date); chop($hw); print $date; @darr = split(/\ +/,$date); @harr = split(/\ +/,$hw); $dnow = $darr[0] . " " . $darr[1] . " " . $darr[2] . " " . $darr[3]; $hnow = $harr[0] . " " . $harr[1] . " " . $harr[2] . " " . $harr[3]; system "date --set=\"$hnow\"";
-- [EMAIL PROTECTED] mailing list
