From owner-freebsd-questions@FreeBSD.ORG Sat Apr 15 00:04:37 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 CEE7816A409 for ; Sat, 15 Apr 2006 00:04:37 +0000 (UTC) (envelope-from jdow@earthlink.net) Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 249C143D45 for ; Sat, 15 Apr 2006 00:04:37 +0000 (GMT) (envelope-from jdow@earthlink.net) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=rkV6BNQCF4dDqWZUhshIU6+FKq0H/3wQnbcrGqgYa6kwQbFSR1hZe2C0E+69Hrea; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP; Received: from [71.116.162.101] (helo=Wednesday) by elasmtp-banded.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1FUYH9-0001YP-4S for freebsd-questions@freebsd.org; Fri, 14 Apr 2006 20:04:31 -0400 Message-ID: <060701c66020$2b8a6d30$0225a8c0@Wednesday> From: "jdow" To: References: <5507.208.11.134.3.1145029242.squirrel@mail.dfwlp.com><20060414155343.GD89228@dan.emsphone.com> <200604150051.10024.list-freebsd-2004@morbius.sent.com> Date: Fri, 14 Apr 2006 17:04:30 -0700 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-ELNK-Trace: bb89ecdb26a8f9f24d2b10475b571120a09c3d40d05eef5480a37a6113424e283788860f0b40a802350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 71.116.162.101 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: Sat, 15 Apr 2006 00:04:37 -0000 From: "RW" > 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. Feed it several server names and try it. Use the -q option so it will not attempt to modify time and the -v option to see what it does in more detail. {^_^}