| Re: [chrony-users] Time synchronisation over a high-latency packet radio network |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
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.
--
Miroslav Lichvar
--
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.