Thanks, "Setting 'poll 1 filter 1' reduces the source selection time to 20 seconds from 40 seconds. Is there a way to dynamically adjust these parameters? For example, at startup, the settings can be 'poll 1 filter 1' and my application sends samples every second. After the source is selected, my application can slow down to send samples once every 5 seconds, and the 'filter' can return to its default value and 'poll' can be set to 3." Alternatively, can I always use "poll 1 filter 1" irrespective of my application sending samples every seconds or once every 5 seconds?
What are the drawbacks of setting 'poll 1 filter 1'? Thanks again Amol ________________________________ From: Miroslav Lichvar <mlich...@redhat.com> Sent: Wednesday, July 31, 2024 2:22 PM To: chrony-users@chrony.tuxfamily.org <chrony-users@chrony.tuxfamily.org> Subject: Re: [chrony-users] Using cellular network clock as refclock in chrony On Wed, Jul 31, 2024 at 08:42:52AM +0000, Amol Lad wrote: > refclock SOCK /var/run/chrony.cellular.sock precision 1 prefer poll 3 refid > MODM > > (I tried reducing the poll to 1 but this does not seem to make any difference) Try adding "filter 1" to reduce the number of samples required per poll. Unlike with SHM, chronyd doesn't know how many SOCK samples there will be per poll, so it doesn't adjust the filter length automatically. -- Miroslav Lichvar -- To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-users-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org. ________________________________ The information in this email communication (inclusive of attachments) is confidential to 4RF Limited and the intended recipient(s). If you are not the intended recipient(s), please note that any use, disclosure, distribution or copying of this information or any part thereof is strictly prohibited and that the author accepts no liability for the consequences of any action taken on the basis of the information provided. If you have received this email in error, please notify the sender immediately by return email and then delete all instances of this email from your system. 4RF Limited will not accept responsibility for any consequences associated with the use of this email (including, but not limited to, damages sustained as a result of any viruses and/or any action or lack of action taken in reliance on it).
