Date: Fri, 12 Apr 2002 00:59:03 -0400 (EDT) From: doug <doug@safeport.com> To: wes chow <wes@woahnelly.net> Cc: Peter Leftwich <Hostmaster@Video2Video.Com>, FreeBSD Questions <FreeBSD-Questions@FreeBSD.ORG> Subject: Re: grr, stupid springforwardfallback (timed) Message-ID: <Pine.BSF.3.96.1020412004956.68604A-100000@fledge.watson.org> In-Reply-To: <20020411224909.B3095-100000@hitchcock.woahnelly.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.1020412004956.68604A-100000>