Re: Timezone problems on -current

tech-lists <[email protected]> Tue, 4 May 2021 02:13:55 +0100

Newsgroups	gmane.os.freebsd.devel.arm
Message-ID	<[email protected]>

Hi,

On Mon, May 03, 2021 at 08:34:42AM -0700, bob prohaska wrote:
>It seems that the timezone gets screwed up each time the OS is
>upgraded on a Pi4  via sources on -current. ntpdate is working, but the

[snip]

On all my VMs which are mostly 12.2-p6/amd64 I run ntpdate and ntpd 
and they'll all return a line like this:

ntpdate[532]: step time server 178.79.145.244 offset -3598.919836 sec

when rebooted. I have this in my /etc/rc.conf:

# ntpd
ntpdate_enable="YES"
ntpdate_flags="-b"
ntpdate_hosts="uk.pool.ntp.org"
ntpd_enable="YES"
ntpd_sync_on_start="YES"

if those lines are missing, the clock will show a majorly drifted value
on reboot, and unless ntpd is told to, it won't set the proper time
immediately. It'll do it in small increments over a long time. With my
config, when login appears, the time is correctly set. Maybe it doesn't
need the ntpdate lines. I understand that ntpdate is being phased out?
Anyway, it seems to work, for now.

-- 
J.

signature.asc (application/pgp-signature, 833 B)