RE: [EXTERNAL] Re: [chrony-users] Syncing time as with a single request

2020-02-04 Thread Gustav Krantz
From: Lonnie Abelbeck  
Sent: Tuesday, February 4, 2020 2:31 PM

>You need to build the "the current development code in git" for this new 
>'maxsamples 1' feature. No official release with this new feature is available 
>yet.

Thanks, for the quick reply. I missed that detail. Will give it a shot.
Gustav

--
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.



Re: [EXTERNAL] Re: [chrony-users] Syncing time as with a single request

2020-02-04 Thread Lonnie Abelbeck



> On Feb 4, 2020, at 4:12 PM, Gustav Krantz  wrote:
> 
> From: Miroslav Lichvar  
> Sent: Tuesday, January 28, 2020 12:36 AM
> 
>> The current development code in git supports a single-sample 
>> selection/update mode, enabled by setting maxsample to 1, but it's meant to 
>> be used only in the "ntpdate" mode (-q/-Q option) as it doesn't adjust the 
>> frequency of the clock. You could use it for the initial correction before 
>> normally starting chronyd.
>> 
>> # chronyd -q 'pool pool.example.com maxsamples 1 iburst'
> 
> Hello Miroslav,
> Thank you for your answer. This is exactly what I am looking for, however it 
> seems that what you are suggesting is not working.
> 
> x:~$ sudo chronyd -q 'pool 0.pool.ntp.org maxsamples 1 iburst'
> 2020-02-04T22:03:05Z chronyd version 3.3 starting (+CMDMON +NTP +REFCLOCK 
> +RTC -PRIVDROP -SCFILTER -SIGND +ASYNCDNS -SECHASH +IPV6 -DEBUG)
> 2020-02-04T22:03:05Z Initial frequency 6.501 ppm
> 2020-02-04T22:05:22Z No suitable source for synchronisation
> 2020-02-04T22:05:22Z chronyd exiting
> 
> Removing the maxsamples 1, will allow a sync, but with assumingly several 
> requests sent with a wait in between.
> x:~$ sudo chronyd -q 'pool 0.pool.ntp.org iburst'
> 2020-02-04T21:58:58Z chronyd version 3.3 starting (+CMDMON +NTP +REFCLOCK 
> +RTC -PRIVDROP -SCFILTER -SIGND +ASYNCDNS -SECHASH +IPV6 -DEBUG)
> 2020-02-04T21:58:58Z Initial frequency 6.501 ppm
> 2020-02-04T21:59:03Z System clock wrong by 0.001764 seconds (step)
> 2020-02-04T21:59:03Z chronyd exiting
> 
> Do you have any ideas of what could be the issue?
> 
> Thanks,
> Gustav Krantz

You need to build the "the current development code in git" for this new 
'maxsamples 1' feature. No official release with this new feature is available 
yet.

Lonnie



--
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.



RE: [EXTERNAL] Re: [chrony-users] Syncing time as with a single request

2020-02-04 Thread Gustav Krantz
From: Miroslav Lichvar  
Sent: Tuesday, January 28, 2020 12:36 AM

>The current development code in git supports a single-sample selection/update 
>mode, enabled by setting maxsample to 1, but it's meant to be used only in the 
>"ntpdate" mode (-q/-Q option) as it doesn't adjust the frequency of the clock. 
>You could use it for the initial correction before normally starting chronyd.
>
># chronyd -q 'pool pool.example.com maxsamples 1 iburst'

Hello Miroslav,
Thank you for your answer. This is exactly what I am looking for, however it 
seems that what you are suggesting is not working.

x:~$ sudo chronyd -q 'pool 0.pool.ntp.org maxsamples 1 iburst'
2020-02-04T22:03:05Z chronyd version 3.3 starting (+CMDMON +NTP +REFCLOCK +RTC 
-PRIVDROP -SCFILTER -SIGND +ASYNCDNS -SECHASH +IPV6 -DEBUG)
2020-02-04T22:03:05Z Initial frequency 6.501 ppm
2020-02-04T22:05:22Z No suitable source for synchronisation
2020-02-04T22:05:22Z chronyd exiting

Removing the maxsamples 1, will allow a sync, but with assumingly several 
requests sent with a wait in between.
x:~$ sudo chronyd -q 'pool 0.pool.ntp.org iburst'
2020-02-04T21:58:58Z chronyd version 3.3 starting (+CMDMON +NTP +REFCLOCK +RTC 
-PRIVDROP -SCFILTER -SIGND +ASYNCDNS -SECHASH +IPV6 -DEBUG)
2020-02-04T21:58:58Z Initial frequency 6.501 ppm
2020-02-04T21:59:03Z System clock wrong by 0.001764 seconds (step)
2020-02-04T21:59:03Z chronyd exiting

Do you have any ideas of what could be the issue?

Thanks,
Gustav Krantz

--
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.