Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 20 Aug 2000 16:49:51 -0600
From:      Chris Fedde <chris@fedde.littleton.co.us>
To:        Len Conrad <lconrad@Go2France.com>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: some machines won't run xntpd 
Message-ID:  <200008202249.e7KMnpj00746@fedde.littleton.co.us>
In-Reply-To: <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?
Syslog uses the loghub machine time stamp rather than the origionator.
Also it could have something to do with CMOS clock setting and the
existance or absence of /etc/wall_cmos_clock.

chris
--
    Chris Fedde
    303 773 9134


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?200008202249.e7KMnpj00746>