From owner-freebsd-questions@FreeBSD.ORG Tue Jul 15 16:07:28 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 19DB837B401 for ; Tue, 15 Jul 2003 16:07:28 -0700 (PDT) Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C4C643F3F for ; Tue, 15 Jul 2003 16:07:27 -0700 (PDT) (envelope-from stanb@panix.com) Received: from panix.com (brillig.panix.com [166.84.1.76]) by mail1.panix.com (Postfix) with ESMTP id 80EFE4883D; Tue, 15 Jul 2003 19:07:26 -0400 (EDT) Received: from teddy.fas.com (pcp01010374pcs.mplsnt01.sc.comcast.net [68.58.176.69]) by panix.com (Postfix) with ESMTP id 670952AA3D; Tue, 15 Jul 2003 19:07:26 -0400 (EDT) Received: from stan by teddy.fas.com with local (Exim 3.36 #1 (Debian)) id 19cYtK-0006HK-00; Tue, 15 Jul 2003 19:07:26 -0400 Date: Tue, 15 Jul 2003 19:07:26 -0400 From: stan To: Lowell Gilbert Message-ID: <20030715230726.GB24083@teddy.fas.com> Mail-Followup-To: Lowell Gilbert , Free BSD Questions list References: <20030714231604.GA27924@teddy.fas.com> <44oezw6kdk.fsf@be-well.ilk.org> <20030715133259.GA10641@teddy.fas.com> <44el0rpqlj.fsf@be-well.ilk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44el0rpqlj.fsf@be-well.ilk.org> X-Editor: gVim X-Operating-System: Debian GNU/Linux X-Kernel-Version: 2.4.21 X-Uptime: 19:03:49 up 29 days, 6:06, 2 users, load average: 0.00, 0.00, 0.00 User-Agent: Mutt/1.5.4i Sender: Stan Brown cc: Free BSD Questions list 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 23:07:28 -0000 On Tue, Jul 15, 2003 at 02:55:20PM -0400, Lowell Gilbert wrote: > 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. Interesting. It does not do this under Linux, and I was assuming that the behavior would be the same on FreeBSD. I expect that now that I know thta, I understnad what happened to me. On reboot with the CMOS clock set incorectly ntpd failed to satrt. I thien ran ntpdate by hand. But of course ntpd was no longer running to set the hardware clock. Thanks for making me think this thru. -- "They that would give up essential liberty for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin