Date: Tue, 04 May 2021 08:42:14 -0600 From: Ian Lepore <ian@freebsd.org> To: bob prohaska <fbsd@www.zefox.net>, freebsd-arm@freebsd.org Subject: Re: Timezone problems on -current Message-ID: <8e4843ce80e9bc005da5ca42d43e0bc34ce2c6ff.camel@freebsd.org> In-Reply-To: <20210504015222.GE37236@www.zefox.net> References: <20210503153442.GB37236@www.zefox.net> <YJCf00lvkp%2BUyamn@cloud.zyxst.net> <20210504015222.GE37236@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2021-05-03 at 18:52 -0700, bob prohaska wrote: > On Tue, May 04, 2021 at 02:13:55AM +0100, tech-lists wrote: > > > > # ntpd > > ntpdate_enable="YES" > > ntpdate_flags="-b" > > ntpdate_hosts="uk.pool.ntp.org" > > ntpd_enable="YES" > > ntpd_sync_on_start="YES" > > > > Up to now I've used only the line > ntpdate_enable="YES" > and it's been enough to keep the clock sane. On the last reboot > it appears ntpdate either didn't run or failed silently. The most > obvious suspect is a wireless ethernet bridge that might be saying > it's up before the access point is responsive. > > I'll have to do a few test reboots when the machine becomes idle. > I know ntpdate works sometimes, but perhaps not always. > > Thanks for writing, > > bob prohaska > You don't need to be running ntpdate at all. ntpd_sync_on_start gives you the same effect... it allows ntpd to step the clock any required amount, one time at startup. It's useful for systems that don't have a battery-backed clock. I like to set kern.timecounter.stepwarnings=1 in /etc/sysctl.conf so I have a record in syslog of when ntpd steps the clock. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8e4843ce80e9bc005da5ca42d43e0bc34ce2c6ff.camel>