Date: Tue, 22 Apr 2003 14:44:13 -0500 From: David Kelly <dkelly@hiwaay.net> To: Charles Swiger <cswiger@mac.com> Cc: FreeBSD-Questions@freebsd.org Subject: Re: Accurate time without a network connection? Message-ID: <20030422194413.GC13774@grumpy.dyndns.org> In-Reply-To: <4B518202-74F8-11D7-BCB7-003065ABFD92@mac.com> References: <20030422184554.GA13432@grumpy.dyndns.org> <4B518202-74F8-11D7-BCB7-003065ABFD92@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 22, 2003 at 03:26:19PM -0400, Charles Swiger wrote: > > Ok. If you run NTPD with only the local hardware clock for a > reference, wait for a week, and then see how the intrinsic drift of the > hardware compares with "real time" (using your watch or some other time > source), you can adjust /etc/ntp.drift by hand. This isn't going to be > perfect, but it's going to be much more accurate than doing nothing. Good. But already tried that. The situation is multiple systems have to run with something near the same time, but no bidirectional contact. And need to operate for years. Letting ntpd tune itself and then free run works much better than the system clock alone but only good for weeks, not months. As for exactly what time the systems have, it doesn't much matter as long as they all have the same time. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030422194413.GC13774>