开云体育

Charles -

There are two different time synch services available in the Debian distribution used as a base for the Rpi.

One is the service you've asked about , known to the system as "systemd-timesyncd.service".
The other is the service that is being used to sync time, known to the system as "ntp.service".

The command "timedatectl" with no arguments examines the system clock in the context of "systemd-timesyncd.service", and is equivalent to "timedatectl status".
Typing "timedatectl show", on the other hand, shows different output.

Examining the current state of the services managed by the system (a.k.a "daemons" or "demons") is done by the command systemctl.

To examine both of the services mentioned above, type the following command in a console (terminal):
systemctl list-units --all ntp.service systemd-timesyncd.service

On my Rpi 4B, using the 1.5 HamPi distribution, here is the leading few lines of output
UNIT????????????????????????????????? LOAD?? ACTIVE?? SUB?????? DESCRIPTION??????????????? ?
ntp.service????????????????????????? loaded??? active??????? running? Network Time Service?????? ?
systemd-timesyncd.service loaded?? inactive???? dead?????? Network Time Synchronization

This shows that the "ntp.service" is up and running, doing it's task of syncing the clock, as specified by /etc/ntp.conf .
To obtain more details about the status of ntp.service, the command "ntpq" can be used, but the various options assume wizard-status on the distributed time service implementation and function.

A useful command is "ntpq -n -c lpeers" , where the output is in dotted-quad IP addresses. The leading asterisk indicates the current time source, the plus indicates "candidate" to become a source, and the minus indicates "outlier" status.

Hope this helps clear up any confusion. Post any follow-up questions in this thread, and I'll attempt to answer.

Walt
W1ALT
(Unix/linux nerd for most of my working life)