From owner-freebsd-questions@FreeBSD.ORG  Tue Jul 15 05:32:26 2003
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
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 DC1A737B401
	for <freebsd-questions@freebsd.org>;
	Tue, 15 Jul 2003 05:32:26 -0700 (PDT)
Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C74C043F93
	for <freebsd-questions@freebsd.org>;
	Tue, 15 Jul 2003 05:32:25 -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 (sccrmhc13) with ESMTP
          id <20030715123225016000tumse>; Tue, 15 Jul 2003 12:32:25 +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 h6FCWOP0086217;
	Tue, 15 Jul 2003 08:32:24 -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 h6FCWN4Q086214;
	Tue, 15 Jul 2003 08:32:23 -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>
From: Lowell Gilbert <freebsd-questions-local@be-well.no-ip.com>
Date: 15 Jul 2003 08:32:23 -0400
In-Reply-To: <20030714231604.GA27924@teddy.fas.com>
Message-ID: <44oezw6kdk.fsf@be-well.ilk.org>
Lines: 20
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: stan <stanb@panix.com>
Subject: Re: Seting the hardware clock
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: freebsd-questions@freebsd.org
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jul 2003 12:32:27 -0000

stan <stanb@panix.com> writes:

> ;m struggling with getting the hardware clock (BIOS clock) equal to the
> kernels time.
> 
> On my Linux boxes a utility called hwclock is run on the way down to
> synchronize the 2.
> 
> The problem I'm running into is that if the time on the system gets to far
> out of date for ntpd to bring it into synch, then I can update the kernels
> clock with ntpdate. But when I reboot the old incorrect time comes back.
> 
> I ran into this during some software testing, that required setting the
> clock pretty far off of real time, and it was a PIA to get the machine back
> to the correct time.
> 
> How _should_ this be handled?

Most people run ntpdate before starting ntpd.
The rc.conf enable flags for the two programs support this.