Date: Sat, 26 Apr 2003 00:54:55 -0400 From: Wade Majors <wade@ezri.org> To: freebsd-questions@freebsd.org Subject: Re: Time Problem in 5.0 Message-ID: <3EAA111F.6090409@ezri.org> In-Reply-To: <3EA9EDF4.9000702@potentialtech.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3EAA111F.6090409>