Date: Wed, 22 Sep 2004 23:33:09 +0200 From: Emanuel Strobl <Emanuel.Strobl@gmx.net> To: freebsd-questions@freebsd.org Cc: Bill Moran <wmoran@potentialtech.com> Subject: Re: Ntpd assistance Message-ID: <200409222333.13968.Emanuel.Strobl@gmx.net> In-Reply-To: <20040922172717.280ed3af.wmoran@potentialtech.com> References: <415197F9.3080901@verizon.net> <200409222152.12582.Emanuel.Strobl@gmx.net> <20040922172717.280ed3af.wmoran@potentialtech.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Am Mittwoch, 22. September 2004 23:27 schrieb Bill Moran: > Emanuel Strobl <Emanuel.Strobl@gmx.net> wrote: > > Am Mittwoch, 22. September 2004 17:19 schrieb alden.pierre: > > > /etc/rc.conf contains the following: > > > > > > ntpdate_enable="YES" > > > ntpdate_flags="timex.cs.columbia.edu" > > > xntpd_enable="YES" # Run ntpd Network Time Protocol > > > > > > /etc/ntpd.conf contains the following: > > > > ^^^^^^^^^ > > > > Correct me if I'm wrong but doesn't ntpd 4.1 use ntp.conf instead of > > ntpd.conf? > > > > You can try -c /etc/ntpd.conf > > > > -Harry > > In addition to this minor error ... > > I don't believe you can reliably run both ntpdate and xntpd. Besides, This is working because ntpdate is invoked only once at startup, which is, in my case, because of possible empty BIOS-Battery where the date would be wrong for several years which causes ntpd to refuse to adjust the time. I use generally ntpdate at startup before ntpd keeps the kernel time in sync. -Mano > if you plan to run xntpd anyway, just set xntpd_flags="-g" and it will > behave the same as ntpdate at startup, as well as running continually > to ensure your clock stays synced. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD4DBQBBUe+ZBylq0S4AzzwRAgUVAJ92bF3qN3qe9tx631xFOrxQFBNZDQCY0ZSU czUGGdWVWg00MNayrBsHkA== =m+HC -----END PGP SIGNATURE-----home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200409222333.13968.Emanuel.Strobl>