On Sun, Jun 04, 2023 at 12:07:44PM +0200, Torsten Wolf wrote:
> Not sure why the Reach value for the PPS source is 113. A few minuts later
> that value increased to 372, just to go down again afterwards.
That might be due to changing offset between GPS and PPS. Try
adjusting the offset option to
I’m sorry, unlike your prior email, I am unable to read the output in your last
email.
Your prior email looked like this:
——
$ chronyc sourcestats
Name/IP AddressNP NR Span Frequency Freq Skew Offset Std Dev
Apologies, Denny! I am unhappy myself that I do not respect the simplest
mailing list etiquette such as fixed width font, sensitive line wrap and
encoding since I switched to MacOS and Postbox. I guess it's time to get
mutt up and running like in the old Linux days... Back on topic - I hope
That was the hint I needed! The main router the RasPi is connected to
also runs chrony and acts as the timeserver for all local network
clients. However, the script managing that chrony instance had an option
to redirect all NTP traffic through the router. Interesting that I did
not find that
