From owner-freebsd-questions Thu Mar 11 8: 0:16 1999 Delivered-To: freebsd-questions@freebsd.org Received: from europa.salford.ac.uk (europa.salford.ac.uk [146.87.3.2]) by hub.freebsd.org (Postfix) with SMTP id CA47515253 for ; Thu, 11 Mar 1999 07:57:30 -0800 (PST) (envelope-from M.S.Powell@ais.salford.ac.uk) Received: (qmail 14995 invoked by alias); 11 Mar 1999 15:57:09 -0000 Received: (qmail 14988 invoked from network); 11 Mar 1999 15:57:08 -0000 Received: from plato.salford.ac.uk (146.87.255.76) by europa.salford.ac.uk with SMTP; 11 Mar 1999 15:57:08 -0000 Received: (qmail 17655 invoked by alias); 11 Mar 1999 15:57:07 -0000 Delivered-To: catchall-freebsd-questions@freebsd.org Received: (qmail 17646 invoked by uid 141); 11 Mar 1999 15:57:07 -0000 Date: Thu, 11 Mar 1999 15:57:06 +0000 (GMT) From: Mark Powell To: freebsd-questions@freebsd.org Subject: NTP problems. This hardware related? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Running xntpd on a new server in just the same was as I do on every other. However, I noticed this machines clock was way out after a few days. The machine does an "ntpdate -b" at bootup, but can't sync the time. From ntp log: Mar 4 11:32:33 mimas xntpd[111]: offset 0.000000 freq 11.708 poll 6 Mar 4 12:32:33 mimas xntpd[111]: offset 0.000000 freq 11.708 poll 6 Mar 4 13:32:33 mimas xntpd[111]: offset 0.000000 freq 11.708 poll 6 Mar 4 14:32:33 mimas xntpd[111]: offset 0.000000 freq 11.708 poll 6 Mar 4 15:32:33 mimas xntpd[111]: offset 0.000000 freq 11.708 poll 6 The offsets are always o and the 11.708, from /etc/ntp.drift never changes. I changed to having "ntpdate

..." run from cron. Again from ntp log: ntpdate[6478]: step time server 146.87.255.63 offset -2.495694 ntpdate[6481]: step time server 146.87.255.63 offset -2.495796 ntpdate[6489]: step time server 146.87.255.63 offset -2.498253 This machine is gaining ~2.5s every minute! No wonder xntpd can't sync the time. Am I right here? Is that why it's failing? Looking at the clocks at boot up, it would appear that over 40 reboots, the TSC clock has varied from 126668897 to 132002659, a variance of almost 5%. Is this normal? Could this be causing the time problems, and if so is there anyway I can fiddle with tickadj or something to let xntpd work on this machine? Cheers. Mark Powell - System Administrator (UNIX) - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key M.S.Powell@ais.salfrd.ac.uk (spell salford correctly to reply to me) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message