On Wed 06 Mar 2024 at 07:07:36 (-0500), Greg Wooledge wrote:
> On Wed, Mar 06, 2024 at 07:37:09AM +0200, Teemu Likonen wrote:
> > It seems that you have solved the problem but here is another hint.
> > "timedatectl" is a good high-level tool for querying and adjusting time
> > settings. Without command-line arguments it prints a lot of useful info:
> >
> > $ timedatectl
> > Local time: ke 2024-03-06 07:33:00 EET
> > Universal time: ke 2024-03-06 05:33:00 UTC
> > RTC time: ke 2024-03-06 05:33:00
> > Time zone: Europe/Helsinki (EET, +0200)
> > System clock synchronized: yes
> > NTP service: active
> > RTC in local TZ: no
> >
> > See "timedatectl -h" or manual page for more info.
>
> This is a great hint, but be warned that it doesn't quite know about
> NTP services other than systemd-timesyncd. If you're running ntpsec,
> for example, it'll simply say:
>
> System clock synchronized: yes
> NTP service: n/a
Note also that it only shows the system's time zone, and not
necessarily that of the user running it:
$ timedatectl ; echo ; date
Local time: Wed 2024-03-06 19:18:58 UTC
Universal time: Wed 2024-03-06 19:18:58 UTC
RTC time: Wed 2024-03-06 19:18:58
Time zone: Etc/UTC (UTC, +0000)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
Wed Mar 6 13:18:58 CST 2024
$
Cheers,
David.
