On Mon, Jan 08, 2007 at 05:06:19PM -0500, sean wrote: > ntp-4.2.2p4-2.fc7.x86_64 > > I set time and date this morning. Now at 16;45 local time, I > show 23:09 on the computer. This is not likely ntp. Probably something is messing up your clocks. Kernel is pickup up a clock which is broken? When differences are too big then ntp is giving up. A quick check. Set clock correctly, do not start ntpd at all. Is time sane after a while then? > Jan 8 16:49:25 localhost ntpd[10919]: frequency initialized > 0.000 PPM from /var/lib/ntp/drift 0.000 PPM??? > > ntpq> pe > remote refid st t when poll reach delay offset jitter > ============================================================================== > 58.73.137.250 .GPS. 1 u 55 64 177 439.874 -102854 69862.7 > trogdor.ruka.or 64.142.103.194 2 u 61 64 177 192.566 -5814.1 124198. > dnsserver.org 76.169.239.34 2 u 61 64 177 208.446 -6295.5 124753. These are HUGE values for delay, offset and jitter. Do you have anything defined in /etc/ntp/step-tickers so you are trying to change an initial clock value on a startup? I do not think that ntpd will really try to do anything with stuff of that sort. BTW - where is your .LOCL. clock? Did you remove it from a configuration? Not such great idea. Michal -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list