From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 30 16:43:10 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 257E716A41F for ; Tue, 30 Aug 2005 16:43:10 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E9B743D5E for ; Tue, 30 Aug 2005 16:43:09 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id j7UGgn7V041315; Tue, 30 Aug 2005 11:42:49 -0500 (CDT) (envelope-from dan) Date: Tue, 30 Aug 2005 11:42:49 -0500 From: Dan Nelson To: Dag-Erling Smorgrav Message-ID: <20050830164248.GA4337@dan.emsphone.com> References: <4311BDAD.1010803@icyb.net.ua> <20050829.170125.88345281.imp@bsdimp.com> <20050830065931.GD61824@funkthat.com> <86wtm3eec2.fsf@xps.des.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86wtm3eec2.fsf@xps.des.no> X-OS: FreeBSD 5.4-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.9i Cc: freebsd-hackers@freebsd.org, dmitry.mityugov@gmail.com Subject: Re: ntpd and cmos clock update X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 16:43:10 -0000 In the last episode (Aug 30), Dag-Erling Smorgrav said: > John-Mark Gurney writes: > > but since we don't set the TOD chip upon reboot, all the work that > > ntpd did over the previous reboot is lost... > > echo 'ntpdate_enable="YES"' >>/etc/rc.conf I think he meant shutdown instead of reboot. ntpd will step the clock itself on bootup if it needs to (although not as quickly at ntpdate certainly). Just calling resettodr during shutdown would be the easiest solution, I think. Or have a kernel timer fire that calls it every 24 hours. -- Dan Nelson dnelson@allantgroup.com