From owner-freebsd-questions@FreeBSD.ORG Mon Jul 14 16:16:37 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 085DB37B401 for ; Mon, 14 Jul 2003 16:16:37 -0700 (PDT) Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DAAE43F3F for ; Mon, 14 Jul 2003 16:16:36 -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 842D148702 for ; Mon, 14 Jul 2003 19:16:35 -0400 (EDT) Received: from teddy.fas.com (pcp01010374pcs.mplsnt01.sc.comcast.net [68.58.176.69]) by panix.com (Postfix) with ESMTP id 4F0C12AA3C for ; Mon, 14 Jul 2003 19:16:05 -0400 (EDT) Received: from stan by teddy.fas.com with local (Exim 3.36 #1 (Debian)) id 19cCY8-0007Hp-00 for ; Mon, 14 Jul 2003 19:16:04 -0400 Date: Mon, 14 Jul 2003 19:16:04 -0400 From: stan To: Free BSD Questions list Message-ID: <20030714231604.GA27924@teddy.fas.com> Mail-Followup-To: Free BSD Questions list Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Editor: gVim X-Operating-System: Debian GNU/Linux X-Kernel-Version: 2.4.21 X-Uptime: 19:11:14 up 28 days, 6:13, 2 users, load average: 0.04, 0.03, 0.01 User-Agent: Mutt/1.5.4i Sender: Stan Brown Subject: 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: Mon, 14 Jul 2003 23:16:37 -0000 ;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? -- "They that would give up essential liberty for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin