Hello,
2016-01-12 18:49 GMT+01:00 Miroslav Lichvar :
> On Tue, Jan 12, 2016 at 06:31:13PM +0100, Hector Oron wrote:
> Hm, with minpoll 8 (256 seconds) chronyd should have 3 samples per
> source after about 9 minutes, so I'm not sure why 17 minutes is not
> enough.
Probabl
Hello,
2016-01-12 14:33 GMT+01:00 Miroslav Lichvar :
> How long ago was the clock set to this date? If chronyd hadn't had a
> chance to make new measurements in that interval, the makestep command
> would not fix the offset as chronyd would still think the date is
> correct. It would be useful to
Hello,
2016-01-12 17:26 GMT+01:00 Bill Unruh :
> On Tue, 12 Jan 2016, Hector Oron wrote:
>> Hello,
>>
>> As I read on an old post here:
>>
>> http://listengine.tuxfamily.org/chrony.tuxfamily.org/chrony-users/2014/10/msg4.html
>>
>> The rec
Hello,
2016-01-12 14:33 GMT+01:00 Miroslav Lichvar :
> On Tue, Jan 12, 2016 at 01:26:13PM +0100, Hector Oron wrote:
>> > If measurements were made not too long before the shutdown, i.e.
>> > chronyd knows the current offset and is correcting it by slewing
>> > yo
Hello,
2016-01-12 13:05 GMT+01:00 Miroslav Lichvar :
> On Tue, Jan 12, 2016 at 11:58:30AM +0100, Hector Oron wrote:
>> The recommended way to be able to force a sync is to generate a
>> burst and wait 10 sec for measurements to complete, then do the
>> stepping on
Hello,
As I read on an old post here:
http://listengine.tuxfamily.org/chrony.tuxfamily.org/chrony-users/2014/10/msg4.html
The recommended way to be able to force a sync is to generate a
burst and wait 10 sec for measurements to complete, then do the
stepping on the clock.
My requi
