Date: Tue, 30 Aug 2005 08:37:31 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: gurney_j@resnet.uoregon.edu Cc: freebsd-hackers@freebsd.org, dmitry.mityugov@gmail.com Subject: Re: ntpd and cmos clock update Message-ID: <20050830.083731.122805682.imp@bsdimp.com> In-Reply-To: <20050830065931.GD61824@funkthat.com> References: <b7052e1e05082905206b1f0f31@mail.gmail.com> <20050829.170125.88345281.imp@bsdimp.com> <20050830065931.GD61824@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20050830065931.GD61824@funkthat.com>
John-Mark Gurney <gurney_j@resnet.uoregon.edu> writes:
: Warner Losh wrote this message on Mon, Aug 29, 2005 at 17:01 -0600:
: > In message: <b7052e1e05082905206b1f0f31@mail.gmail.com>
: > Dmitry Mityugov <dmitry.mityugov@gmail.com> writes:
: > : That's why I always thought that ntpd did not work in FreeBSD 5.x!
: >
: > ntpd works perfectly on FreebSD 5.x
:
: I think he refers to the fact that after a reboot, the time has to be
: adjusted by n seconds, so obviously the time that FreeBSD thought it
: was just before the reboot was just as far off... hence ntpd wasn't
: working...
When ntpd is running, ntpd sets the time. The TODR is just something
that gets things kinda close for ntpd to actually do its work. Of
course, since all my 5.x experience is done on machines that get the
time from GPS and the local time doesn't matter at all, I might not
have noticed something like that.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050830.083731.122805682.imp>