| Re: [chrony-users] Time synchronisation over a high-latency packet radio network |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Time synchronisation over a high-latency packet radio network
- From: Stuart Longland <stuartl@xxxxxxxxxxxxxxxxxx>
- Date: Mon, 13 May 2019 17:35:41 +1000
- Autocrypt: addr=stuartl@xxxxxxxxxxxxxxxxxx; prefer-encrypt=mutual; keydata= mDMEWlBsJhYJKwYBBAHaRw8BAQdAbPG54xFTFq9KRO0BDQdf1fct/ffRc919iCYkX1CEwZG0 KlN0dWFydCBMb25nbGFuZCAoVks0TVNMKSA8bWVAdms0bXNsLmlkLmF1PoiWBBMWCAA+AhsD BQsJCAcCBhUICQoLAgQWAgMBAh4BAheAFiEECUejgYXxHTwl+RpiaqMu+xgHm6oFAlwyu6kF CQWktoMACgkQaqMu+xgHm6ozHgD/RPLD44R4VPDUAlBq0KPKN7GAHeLVXqdWSFVVTy4RXCIB ANoIq1SMpjnDnu/Is7XFYi5K+91RDDClDXk3nqBOmQoMtCxTdHVhcnQgTG9uZ2xhbmQgPHN0 dWFydGxAbG9uZ2xhbmRjbGFuLmlkLmF1PoiWBBMWCAA+AhsDBQsJCAcCBhUICQoLAgQWAgMB Ah4BAheAFiEECUejgYXxHTwl+RpiaqMu+xgHm6oFAlwyu6kFCQWktoMACgkQaqMu+xgHm6pm cAD/Z6yO5siKNfsd/4aHtDLymPb7vQAF5sxLPToifVsdV4EBAJtaGYk76llZ1ebGzlWcI2td UagCIDcY0bE42cbaTVQJtCRTdHVhcnQgTG9uZ2xhbmQgPHN0dWFydGxAdnJ0LmNvbS5hdT6I lgQTFggAPgIbAwULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgBYhBAlHo4GF8R08JfkaYmqjLvsY B5uqBQJcMrupBQkFpLaDAAoJEGqjLvsYB5uquFgBAIyVd2U4E6nP3BO6H7nsMXR8zNZ66ytG NY/yTPDEI/5WAP9Vw5mkHozKzftrPcTxXjU1G7J35+SgoeRCMlZjc3Q5Drg4BFpQbCYSCisG AQQBl1UBBQEBB0AXTrWka0X/ky9LUxO+1eV3xWQV/3DrKy0VBp28IaDjfgMBCAeIfgQYFggA JgIbDBYhBAlHo4GF8R08JfkaYmqjLvsYB5uqBQJcMru3BQkFpLaRAAoJEGqjLvsYB5uqwKAA /jkHd4yASgOjpoMm9XVqRsd1JwiDwolJT9dBNTZ4xnsAAP4m+XWmPCd5hu7LuYS6n16jnCzZ O+RROnLs5EnmgztzCQ==
- Openpgp: id=0947A38185F11D3C25F91A626AA32EFB18079BAA; url=https://stuartl.longlandclan.id.au/key.asc
On 13/5/19 5:08 pm, Miroslav Lichvar wrote:
> On Sun, May 12, 2019 at 03:51:43PM +1000, Stuart Longland wrote:
>> I gave this a shot, but had no joy:
>>> root@hackerlab:~# chronyd -q -t 30 "server 127.0.0.1 port 3123"
>>> 2016-11-03T18:02:55Z chronyd version 3.0 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SECHASH +SIGND +ASYNCDNS +IPV6 -DEBUG)
>>> 2016-11-03T18:02:55Z Initial frequency 26.917 ppm
>>> 2016-11-03T18:03:25Z chronyd exiting
>>
>> I'll keep it on one side though, as it may be part of the solution overall.
>
> 30 seconds is too short for the default minpoll/maxpoll with no
> iburst. You would also need to increase the maxjitter and maxdistance
> values if you need them in normal operation. I think it's usually
> better to just start the normal chronyd instance and wait for the sync
> with the chronyc waitsync command instead of using -q to avoid wasting
> those measurements.
Actually, silly thought… the `chronyc` command, is there a way to make
the `waitsync` call via an API of some kind (HTTP-based perhaps?).
It'd be really handy to know for sure the clock is set rather than just
checking to see that the current system time is later than the age of my
application.
The response codes I've seen out of `chronyc` hint at something HTTP
based (maybe via a Unix-domain socket), which would work real well since
I'm using the `asyncio` event loop.
--
Stuart Longland (aka Redhatter, VK4MSL)
I haven't lost my mind...
...it's backed up on a tape somewhere.
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.