From owner-freebsd-questions@FreeBSD.ORG Tue Jul 15 11:55:23 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D33F37B405 for ; Tue, 15 Jul 2003 11:55:23 -0700 (PDT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id D75FF43F75 for ; Tue, 15 Jul 2003 11:55:21 -0700 (PDT) (envelope-from freebsd-questions-local@be-well.no-ip.com) Received: from be-well.ilk.org (be-well.no-ip.com[66.30.200.37]) by comcast.net (sccrmhc12) with ESMTP id <2003071518552101200ah96he>; Tue, 15 Jul 2003 18:55:21 +0000 Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [66.30.200.37] (may be forged)) by be-well.ilk.org (8.12.9/8.12.9) with ESMTP id h6FItKP0087172 for ; Tue, 15 Jul 2003 14:55:20 -0400 (EDT) (envelope-from freebsd-questions-local@be-well.no-ip.com) Received: (from lowell@localhost) by be-well.ilk.org (8.12.9/8.12.6/Submit) id h6FItKhj087169; Tue, 15 Jul 2003 14:55:20 -0400 (EDT) X-Authentication-Warning: be-well.ilk.org: lowell set sender to freebsd-questions-local@be-well.ilk.org using -f Sender: lowell@be-well.no-ip.com To: freebsd-questions@freebsd.org References: <20030714231604.GA27924@teddy.fas.com> <44oezw6kdk.fsf@be-well.ilk.org> <20030715133259.GA10641@teddy.fas.com> From: Lowell Gilbert Date: 15 Jul 2003 14:55:20 -0400 In-Reply-To: <20030715133259.GA10641@teddy.fas.com> Message-ID: <44el0rpqlj.fsf@be-well.ilk.org> Lines: 17 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: Seting the hardware clock X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2003 18:55:24 -0000 stan writes: > 1. Set the hardware clock to some truly strange time (for testing > software). > > 2. Reboot. > > a. time is set by the BIOS to the wrong time > b. ntpdate corrects this (for the kernel). > c. ntp keeps the time acurate (for this run session). > > 3. shutdown (BIOS time is not corrected). > > See the problem? Nope. ntpd is supposed to set the CMOS clock, and it certainly does so for me.