From owner-freebsd-questions Mon Sep 24 14:38:51 2001 Delivered-To: freebsd-questions@freebsd.org Received: from nebula.anchoragerescue.org (cable-115-7-237-24.anchorageak.net [24.237.7.115]) by hub.freebsd.org (Postfix) with ESMTP id 750AF37B401 for ; Mon, 24 Sep 2001 14:38:38 -0700 (PDT) Received: from there (galaxy.anchoragerescue.org [24.237.7.95]) by nebula.anchoragerescue.org (Postfix) with SMTP id E6244D4 for ; Mon, 24 Sep 2001 13:38:27 -0800 (AKDT) Content-Type: text/plain; charset="iso-8859-1" From: Beech Rintoul To: freebsd-questions@freebsd.org Subject: Clock question Date: Mon, 24 Sep 2001 13:38:27 -0800 X-Mailer: KMail [version 1.3] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20010924213828.E6244D4@nebula.anchoragerescue.org> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have an old 486 on our net that works perfectly except for the clock. ntp resets the time constantly, and this box looks like it gains about 2 minutes an hour. Is there anything I can do to get this under control? The box runs as secondary DNS and works great for that purpose. BTW it's running 4.4-STABLE. Beech To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message