From owner-freebsd-questions Mon Jan 22 9:59:52 2001 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 3207E37B400 for ; Mon, 22 Jan 2001 09:59:34 -0800 (PST) Received: (qmail 17225 invoked by uid 100); 22 Jan 2001 17:59:33 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14956.29957.385328.201918@guru.mired.org> Date: Mon, 22 Jan 2001 11:59:33 -0600 (CST) To: randy // fBSD Cc: questions@freebsd.org Subject: Re: ntpdate and clock In-Reply-To: <76599524@toto.iv> X-Mailer: VM 6.75 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG randy // fBSD types: > Thanks to those who helped with my clock situation. I am using ntpdate as a cron > to update the time every hour. Now it seems that my clock is off by at least -.014 > seconds every hour. Is this normal? Why is off so much in one hour? Well, that amounts to about a 1/3rd of a second a day, which most people would consider to be pretty accurate. Do you have other systems (or clocks) that are noticeably more accurate than that? I'd say ignore it; it's small enough you're not going to get jumps in the clock; just adjustments. Actually, if you're always connected, I'd recommend running ntpd instead of ntpdate out of cron. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message