From owner-freebsd-current Mon Oct 28 15:53:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA18338 for current-outgoing; Mon, 28 Oct 1996 15:53:53 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA18330 for ; Mon, 28 Oct 1996 15:53:40 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.6/8.7.3) with SMTP id PAA28516 for ; Mon, 28 Oct 1996 15:51:06 -0800 (PST) Message-ID: <327546DD.794BDF32@whistle.com> Date: Mon, 28 Oct 1996 15:51:01 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: divergence of clocks Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On our hardware here, we are seeing the clock getting out by some quite large amounts (xntpd is correcting by about a second every 20 minutes.) the RTC however seems to have the correct time (or something closer to it) what are the reasons (for not) and ramifications of, using the RTC for all getimeofday() requests? and can THAT clock be synced using xntpd as well? (I suspect that that RTC clock would not be controllable that way, and that it might be difficult to change the system clock to use the RTC.. I didi note however that the RTC is reported as producing interrupts, so wohat would it take to set Hz to 128 and use that tick instead? (interrupt priorities? etc? etc?) julian