From owner-freebsd-questions@FreeBSD.ORG Fri Apr 14 23:51:14 2006 Return-Path: X-Original-To: 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 806BD16A401 for ; Fri, 14 Apr 2006 23:51:14 +0000 (UTC) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2427643D45 for ; Fri, 14 Apr 2006 23:51:13 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from frontend2.internal (frontend2.internal [10.202.2.151]) by frontend1.messagingengine.com (Postfix) with ESMTP id 2594ED47FEE for ; Fri, 14 Apr 2006 19:51:12 -0400 (EDT) Received: from frontend3.messagingengine.com ([10.202.2.152]) by frontend2.internal (MEProxy); Fri, 14 Apr 2006 19:50:46 -0400 X-Sasl-enc: 3czs5lYvqdazr4/6X948cdrMBXVWO1tIJOGvTlmnRSyh 1145058646 Received: from bb-87-81-140-128.ukonline.co.uk (bb-87-81-140-128.ukonline.co.uk [87.81.140.128]) by frontend3.messagingengine.com (Postfix) with ESMTP id 5ADB476AE for ; Fri, 14 Apr 2006 19:50:46 -0400 (EDT) From: RW To: freebsd-questions@freebsd.org Date: Sat, 15 Apr 2006 00:51:06 +0100 User-Agent: KMail/1.9.1 References: <5507.208.11.134.3.1145029242.squirrel@mail.dfwlp.com> <20060414155343.GD89228@dan.emsphone.com> In-Reply-To: <20060414155343.GD89228@dan.emsphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604150051.10024.list-freebsd-2004@morbius.sent.com> Subject: Re: Proper Method of Time Sync? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2006 23:51:14 -0000 On Friday 14 April 2006 16:53, Dan Nelson wrote: > ntpd takes a while to sync up and by default won't adjust the clock if > it's more than 1000 seconds off, so it's a good idea to enable ntpdate > as well. What bothers me about that is that ntpdate uses a single server to determine the time. I can't recall the reference, but I recently read a "horror story" where someone synched off a timeserver that had been set to 2038 for testing purposes.