I'm running a small home LAN with a single NTP relay (SuSE 9.0) pointing to a public server. The other machines on the LAN point to the relay. Watching the ntp log on the relay though I see that it hasn't been updated by the public server for almost 48 hours. Since my last restart of xntpd it looks like: ################ 15 Jun 18:21:16 ntpd[1543]: ntpd exiting on signal 15 15 Jun 18:24:24 ntpd[4438]: signal_no_reset: signal 17 had flags 4000000 15 Jun 18:24:24 ntpd[4437]: running as uid(74)/gid(65534) euid(74)/egid(65534). 15 Jun 18:24:24 ntpd[4437]: frequency initialized -218.502 from /var/lib/ntp/drift/ntp.drift 15 Jun 18:28:46 ntpd[4437]: time reset -0.390628 s 15 Jun 18:28:46 ntpd[4437]: kernel time discipline status change 41 15 Jun 18:28:46 ntpd[4437]: synchronisation lost ################ However, the drift file is being updated hourly and from ntptime I get: linux:/var/log # ntptime ntp_gettime() returns code 0 (OK) time c47ca1a8.7c1e5000 Thu, Jun 17 2004 18:03:04.484, (.484838), maximum error 605501 us, estimated error 27527 us ntp_adjtime() returns code 0 (OK) modes 0x0 (), offset -1404.000 us, frequency -217.925 ppm, interval 4 s, maximum error 605501 us, estimated error 27527 us, status 0x1 (PLL), time constant 6, precision 1.000 us, tolerance 512 ppm, pps frequency 0.000 ppm, stability 512.000 ppm, jitter 200.000 us, intervals 0, jitter exceeded 0, stability exceeded 0, errors 0. But I admit I don't know what this is telling me. How can I tell if my local relay is working correctly? TIA, Pete