From owner-freebsd-questions@FreeBSD.ORG Sat Apr 26 08:15:43 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 9B87B37B401 for ; Sat, 26 Apr 2003 08:15:43 -0700 (PDT) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 566F143FAF for ; Sat, 26 Apr 2003 08:15:42 -0700 (PDT) (envelope-from kirk@strauser.com) Received: from pooh.honeypot.net.strauser.com (kirk@pooh.honeypot.net [10.0.5.128]) by kanga.honeypot.net (8.12.8/8.12.7) with ESMTP id h3QFFcmL020692 for ; Sat, 26 Apr 2003 10:15:38 -0500 (CDT) (envelope-from kirk@strauser.com) To: freebsd-questions@freebsd.org From: Kirk Strauser Date: Sat, 26 Apr 2003 10:15:37 -0500 In-Reply-To: <20030426024616.GF5143@dan.emsphone.com> (Dan Nelson's message of "Fri, 25 Apr 2003 21:46:16 -0500") Message-ID: <87of2t8f3a.fsf@pooh.honeypot.net> Lines: 14 X-Mailer: Gnus/5.090018 (Oort Gnus v0.18) Emacs/21.3 (gnu/linux) References: <20030424214413.GC90097@grimoire.chen.org.nz> <20030425091950.GA558@dhumketu.homeunix.net> <3EA92FF1.30809@potentialtech.com> <20030425184813.GA674@dhumketu.homeunix.net> <448ytye5xj.fsf@be-well.ilk.org> <3EA9925E.30201@potentialtech.com> <20030425203301.GU45035@dan.emsphone.com> <3EA9D2EC.3040304@potentialtech.com> <20030426010835.GB5143@dan.emsphone.com> <3EA9EDF4.9000702@potentialtech.com> <20030426024616.GF5143@dan.emsphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: Time Problem in 5.0 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: Sat, 26 Apr 2003 15:15:43 -0000 At 2003-04-26T02:46:16Z, Dan Nelson writes: > But ntpdate does serve a useful purpose during bootup. Dan, something I've always wondered about: if a machine runs ntpd during normal operation and is rebooted mainly for periodic maintenance, wouldn't it's hardware clock be accurate to within a few fractions of a second during the downtime? I mean, if my clock it NTP-correct at noon, and I reboot the machine to do a `make installworld', it will be pretty close to accurate when I bring it back online. Since ntpd launches instantly when not in `-q' mode, what's the advantage or point of running ntpdate on boot? Why not just start ntpd as normal and let it smooth over the small amount of drift? -- Kirk Strauser