So I set the clock at 17:05 to match the hardware clock and it's been running about 4 hours now with ntp and here's what I've got. jpschewe at jen:~> date Thu May 28 17:56:36 CDT 2009 jen:/home/jpschewe # hwclock Thu 28 May 2009 09:18:40 PM CDT -0.060009 seconds jen:/home/jpschewe # ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== ntp2.lax-noc.co 204.123.2.5 2 u 21 64 377 15.170 1219819 1154510 skywiley.com 192.43.244.18 2 u 3 64 377 11.136 1227014 1151437 tesla.fireduck. 132.239.1.6 2 u 64 64 377 11.946 1202625 1138791 Jon Schewe wrote: > I've got an opensuse 11.0 system with kernel 2.6.25 and I'm finding that > with or without ntp running the system clock falls way behind. Checking > hwclock shows the correct time, but date is hours behind. Right after > ntp starts up I see this: > jen:/home/jpschewe # ntpq -p > remote refid st t when poll reach delay offset > jitter > ============================================================================== > ntp2.lax-noc.co 204.123.2.5 2 u 19 64 1 16.088 127006. > 3.906 > skywiley.com 192.43.244.18 2 u 18 64 1 16.285 130991. > 3.906 > tesla.fireduck. 132.239.1.6 2 u 17 64 1 13.431 134998. > 3.906 > > At this point I've just set the system time to match the hardware clock > and it's within a minute of reality, however that offset column seem way > to large for something this close. > > Anyone got any ideas? > > -- Jon Schewe | http://mtu.net/~jpschewe If you see an attachment named signature.asc, this is my digital signature. See http://www.gnupg.org for more information. For I am convinced that neither death nor life, neither angels nor demons, neither the present nor the future, nor any powers, neither height nor depth, nor anything else in all creation, will be able to separate us from the love of God that is in Christ Jesus our Lord. - Romans 8:38-39