On Tue, Jan 12, 2016 at 07:05:51PM +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.
>
> Probably I was too quick before, I have redone the test and it seems
> to work
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.
Probably I was too quick before
On Tue, Jan 12, 2016 at 06:31:13PM +0100, Hector Oron wrote:
> chronyc> sources
> 210 Number of sources = 4
> MS Name/IP address Stratum Poll Reach LastRx Last sample
> ===
> ^? der.beste.tiger.ist.sidne 2 8
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 recommended way to be able to force a sync is to genera
On Tue, Jan 12, 2016 at 03:56:31PM +0100, Hector Oron wrote:
> > 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 woul
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
>> > you just need to call chronyc -a mak
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
> > you just need to call chronyc -a makestep to force it to step the
> > clock.
>
> chronyd is run
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 the clock.
>>
>> My requirem
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 the clock.
>
> My requirements need to sync time only at shutdown, but time cannot
> ch
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
On Tue, 12 Jan 2016, Hector Oron wrote:
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 da
On Tue, 12 Jan 2016, Hector Oron wrote:
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 recommended way to be able t
William G. Unruh | Canadian Institute for| Tel: +1(604)822-3273
Physics&Astronomy | Advanced Research | Fax: +1(604)822-5324
UBC, Vancouver,BC | Program in Cosmology | un...@physics.ubc.ca
Canada V6T 1Z1 | and Gravity | www.theory.physics.ubc.ca/
On Tue,
14 matches
Mail list logo
