Date: Sat, 5 Nov 2011 18:19:06 -0400 From: Robert Simmons <rsimmons0@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: ntpdate on boot problem Message-ID: <CA%2BQLa9BV3DCfW4GMJEN4q1nLSJ92yRUCk_VsK-=hWWNy1d6Qng@mail.gmail.com> In-Reply-To: <20111105220349.GA49530@freebsd.org> References: <CA%2BQLa9BOozP544LB7MwzjvXqHPLxgfU0w_nr%2BWv9bQtexFMjbw@mail.gmail.com> <20111105220349.GA49530@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 5, 2011 at 6:03 PM, Alexander Best <arundel@freebsd.org> wrote: > same here. simply add something like the following to your crontab: > > 0 =A0 =A0 =A0 10 =A0 =A0 =A0* =A0 =A0 =A0 * =A0 =A0 =A0 */2 =A0 =A0 /etc/= rc.d/ntpdate onestart I have something similar in my crontab which is not exactly what I need. I want to make sure that the clock is set at every boot because I'm using this as a kerberos server. If the clock is not set properly at boot, kerberos will not work properly until the nightly cron jobs are run and the clock is set then. I need everything working at boot. I can't have a window of problems between boot and midnight or whenever cron runs ntpdate. Rob
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BQLa9BV3DCfW4GMJEN4q1nLSJ92yRUCk_VsK-=hWWNy1d6Qng>