开云体育

I have a Pi 4, and am using the mid December version of Hampi.? (ie the
one before new years update.

the time takes a few moments to set itself, but then deems to drift.

if I type timedatectl
? in a console, I find that systemd-timesyncd.service active: is
indicating that the service is NOT running.

searching on the internet I get all sorts of anwers, most suggesting
installing ntpd invariably followed by another post saying No that is
not the way to do it.

I don't think I have changed any settings from the way hampi was
packaged.? I just made a new sd card of the system about a week before
the new years update, and I noticed that some folks were having problems
with the latest version using wsjt-x so I am hesitant to start fresh
with hampi 2.0.

I am sure that their is a simple thing that I have missed.? the pi is
plugged into my local network, (which then is connected to the net via
DSL)? and the kubuntu pcs on that network seem to manage to stay in sync.

ideas?


--
Charles MacDonald? VA3CPY? ? ? ? ? ? ? ?Stittsville Ontario
cmacd@...? ? ? ? ? ? ? Just Beyond the Fringe
No Microsoft Products were used in sending this e-mail.

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)

In my shack, I have an RPi with a hardware RTC, running weewx and direwolf, and using a serial GPS with 1pps output connected to the RPi serial port, then gpsd and ntp. Keeps excellent time (microsecond stable) and also serves as the NTP server for the house. The biggest deal was making sure shell was disabled on the serial port.

Cheers and 73 - Jon N7UV