From owner-freebsd-questions@FreeBSD.ORG Fri Apr 25 21:54:57 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 D4B4437B401 for ; Fri, 25 Apr 2003 21:54:57 -0700 (PDT) Received: from rrcs-se-24-73-205-166.biz.rr.com (rrcs-se-24-73-205-166.biz.rr.com [24.73.205.166]) by mx1.FreeBSD.org (Postfix) with SMTP id E2D2E43FD7 for ; Fri, 25 Apr 2003 21:54:56 -0700 (PDT) (envelope-from wade@ezri.org) Received: (qmail 62150 invoked from network); 26 Apr 2003 04:54:56 -0000 Received: from unknown (HELO ezri.org) (192.168.0.46) by rrcs-se-24-73-205-166.biz.rr.com with SMTP; 26 Apr 2003 04:54:56 -0000 Message-ID: <3EAA111F.6090409@ezri.org> Date: Sat, 26 Apr 2003 00:54:55 -0400 From: Wade Majors User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030423 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org 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> In-Reply-To: <3EA9EDF4.9000702@potentialtech.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 04:54:58 -0000 Bill Moran wrote: > ntpdate takes a single server and syncs the time with it. If that server > is having difficulty of the sort that makes it's time unreliable, ntpdate > has no way of knowing that and could sync your time to something totally > ridiculous (such as 12:00 AM 1970). This isn't entirelly accurate, as ntpdate can take more than one server as an argument, and will throw out one that is off signifigantly (same as the full blown candidate system in ntpd). ntpdate still serves a purpose during bootup, even if it's functionaly has been incorperated into the daemon. -Wade