Date: Sat, 05 Nov 2011 20:53:04 -0700 From: Carl Johnson <carlj@peak.org> To: freebsd-questions@freebsd.org Subject: Re: ntpdate on boot problem Message-ID: <877h3dzyws.fsf@oak.localnet> References: <CA%2BQLa9BOozP544LB7MwzjvXqHPLxgfU0w_nr%2BWv9bQtexFMjbw@mail.gmail.com> <20111105220349.GA49530@freebsd.org> <CA%2BQLa9BV3DCfW4GMJEN4q1nLSJ92yRUCk_VsK-=hWWNy1d6Qng@mail.gmail.com> <4EB5B9AF.9080101@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Seaman <m.seaman@infracaninophile.co.uk> writes: > On 05/11/2011 22:19, Robert Simmons wrote: >> 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 10 * * */2 /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. > > crontabs have this handy '@reboot' syntax... It's all explained in > crontab(5). Just be aware that 'Run once, at startup', means when 'cron' starts, not just when the system boots, unless they have changed it recently. -- Carl Johnson carlj@peak.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?877h3dzyws.fsf>