From owner-freebsd-questions Thu Apr 11 21:59:25 2002 Delivered-To: freebsd-questions@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id E7A8137B404 for ; Thu, 11 Apr 2002 21:59:13 -0700 (PDT) Received: from localhost (doug@localhost) by fledge.watson.org (8.11.6/8.11.6) with SMTP id g3C4x3X68755; Fri, 12 Apr 2002 00:59:04 -0400 (EDT) (envelope-from doug@safeport.com) X-Authentication-Warning: fledge.watson.org: doug owned process doing -bs Date: Fri, 12 Apr 2002 00:59:03 -0400 (EDT) From: doug X-Sender: doug@fledge.watson.org To: wes chow Cc: Peter Leftwich , FreeBSD Questions Subject: Re: grr, stupid springforwardfallback (timed) In-Reply-To: <20020411224909.B3095-100000@hitchcock.woahnelly.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG That is not exactly true. ntpd will eventually sync up a clock but it has a maximum offset that it will apply. So it you are off by a day or two it will be quite a while before the time will be correct. As said before ntpdate will do this all at once. On my laptop I use both: : # Time Synchronization ntpdate_flags="pemaquid.safeport.com" ntpdate_enable="YES" xntpd_enable="YES" : It seems to work okay. All you ever wanted to know about Time Synchronization Servers: http://www.eecis.udel.edu/~ntp/ On Thu, 11 Apr 2002, wes chow wrote: > > > oh by the way, I believe that ntpd will not automatically sync up a clock > that's way off. You need to run ntpdate once first to get it within a > reasonable error before ntpd will fine tune it. > > > Wes [cut] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message