| 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: Sun, 12 May 2019 15:51:43 +1000
- Openpgp: id=77102FB21549FFDE5E13B83A0C7F53F4F359B8EF; url=https://stuartl.longlandclan.id.au/key.asc
On 8/5/19 1:30 am, Lonnie Abelbeck wrote:
> BTW, at startup our project always steps the time using (8 second timeout would be too low for you):
> --
> chronyd -q -t 8 "server time.example.tld iburst"
> --
> before starting "chronyd" in the background. (no systemd).
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.
--
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.