Re: Timezone problems on -current

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


_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[email protected]"