Date: Wed, 16 Nov 2005 19:57:48 +0300 From: "Andrew P." <infofarmer@gmail.com> To: dick hoogendijk <dick@nagual.st> Cc: Ivailo Tanusheff <i.tanusheff@procreditbank.bg>, fbsdq <freebsd-questions@freebsd.org> Subject: Re: ntpdate Message-ID: <cb5206420511160857v215f91fchb9650618baf903e8@mail.gmail.com> In-Reply-To: <20051116162615.0a3b7707.dick@nagual.st> References: <20051115214101.fb30f4fa.dick@nagual.st> <OF05714E37.11452ACB-ONC22570BB.00538A7F-C22570BB.0053CF95@procreditbank.bg> <20051116162615.0a3b7707.dick@nagual.st>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/16/05, dick hoogendijk <dick@nagual.st> wrote: > On Wed, 16 Nov 2005 17:15:24 +0200 > Ivailo Tanusheff <i.tanusheff@procreditbank.bg> wrote: > > > Why you need to do this? > > Your system is not fully operationl in the time you try to run > > ntpdate. Just edit your /etc/ntp.conf to connect to some time > > servers. Per example mine is: > > [cut very nice example] > > Thank you. I > You are probably right. I'll get rid of ntpdate in rc.conf. > I have two timeservers at the moment. I will look for some more in the > Netherlands. Yours are to far away ;-) Last time I checked ntpd docs there was no way to tell ntpd to set the time to correct at once at startup. Imagine that you've left your box off for a few days. Your clock might get inaccurate by quite a few seconds (about 2-5 minutes a month on some hardware). So ntp either converges for the whole eternity, or just fails to work. Ntpdate at startup solves this problem.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cb5206420511160857v215f91fchb9650618baf903e8>