Re: strange time problem with bullseye
On Wed, Mar 06, 2024 at 12:31:46PM -0500, Roy J. Tellason, Sr. wrote:
> Mine shows:
>
> Local time: Wed 2024-03-06 12:09:44 EST
> Universal time: Wed 2024-03-06 17:09:44 UTC
> RTC time: Wed 2024-03-06 17:20:53
> Time zone: America/New_York (EST, -0500)
> Network time on: yes
> NTP synchronized: no
> RTC in local TZ: no
>
> How do I get the RTC to agree with the right time?
"hwclock -w" to copy the system clock to the hardware clock (RTC). This
should also be done during shutdown, but it doesn't hurt to do it now.
On Wed, Mar 06, 2024 at 07:36:11PM +0200, Teemu Likonen wrote:
> To get operating system's clock have accurate time it needs to be
> synchronized with network time servers via network time protocol (NTP).
> Systemd has that feature. Turn in on with
>
> sudo timedatectl set-ntp true
But *don't* do that if you're using some other NTP program instead of
systemd-timesyncd. Unfortunately, timedatectl does not know about other
NTP programs, and won't report which one you're using. You'll have
to find that out yourself.
Reply to: