Date: Mon, 21 Aug 2000 01:07:44 +0200 From: Len Conrad <lconrad@Go2France.com> To: freebsd-questions@FreeBSD.ORG Subject: Re: some machines won't run xntpd Message-ID: <4.3.2.7.2.20000821010534.02f2af00@mail.Go2France.com> In-Reply-To: <200008202249.e7KMnpj00746@fedde.littleton.co.us> References: <4.3.2.7.2.20000820223714.02ee8f00@mail.Go2France.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>On Sun, 20 Aug 2000 22:54:23 +0200 Len Conrad wrote: > +------------------ > | On 4 of the machines all, is cool. But on 2 machines, messages gives me: > | > | Aug 20 23:35:06 ns2 xntpd[299]: xntpd version=3.4e (beta multicast); > | Tue Dec 28 21:19:34 GMT 1999 (1) > | Aug 20 23:35:06 ns2 xntpd[299]: tickadj = 5, tick = 10000, > tvu_maxslew = 495 > | Aug 20 23:35:06 ns2 xntpd[299]: using xntpd phase-lock loop > | Aug 20 23:39:56 ns2 xntpd[299]: time error -3962.233950 is way too > | large (set clock manually) > | > | .. but the log line timestamp of these two is essentially already "on > | the money", as are the 4 machines that run xntpd just fine. > | > | On these two machines, the ntpd won't unloads (can't see it "ps aux | > | grep ntp"). > | > | What's going on? > +------------------ > >Are these syslog lines collected on the ns2 machine? yes, from the /var/log/messages file >Syslog uses the loghub machine time stamp rather than the origionator. >Also it could have something to do with CMOS clock setting something like what, if CMOS was totally wrong or dead battery? >and the existance or absence of /etc/wall_cmos_clock. what's wall_cmos_clock ? Len http://BIND8NT.MEIway.com: ISC BIND 8.2.2 p5 installable binary for NT4 http://IMGate.MEIway.com: Build free, hi-perf, anti-spam mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.3.2.7.2.20000821010534.02f2af00>