[chrony-dev] [GIT] chrony/chrony.git branch, master, updated. 1.29.1-146-gcf3c7b3

2014-05-20 Thread git
This is an automated email from git. It was enerated because a ref change was pushed to the repository "chrony/chrony.git". The branch, master has been updated via cf3c7b3bd69bfb9c1d06451927168067fb229f7b (commit) via 0b7f64cb338cb512f163b5b6d9ad2bb63d44bc53 (commit) via ec

RE: [chrony-dev] PPS reference clock rejected because of high dispersion

2014-05-20 Thread Hattink, Tjalling [FINT]
> > What I understand is that you have a slightly different meaning for > > the lock directive, maybe my scenario should be a different setting > > than "lock"? Maybe call it "relate"? > > > > So "relate" will mean the PPS is only accepted when the related > > refclock is accepted, but timestamps a

Re: [chrony-dev] PPS reference clock rejected because of high dispersion

2014-05-20 Thread Miroslav Lichvar
On Tue, May 20, 2014 at 02:52:03PM +0200, Hattink, Tjalling [FINT] wrote: > What I understand is that you have a slightly different meaning for the > lock directive, maybe my scenario should be a different setting than > "lock"? Maybe call it "relate"? > > So "relate" will mean the PPS is only acc

RE: [chrony-dev] PPS reference clock rejected because of high dispersion

2014-05-20 Thread Hattink, Tjalling [FINT]
> On Tue, May 20, 2014 at 01:51:59PM +0200, Miroslav Lichvar wrote: > > On Tue, May 20, 2014 at 11:41:39AM +0200, Hattink, Tjalling [FINT] > wrote: > > > When the offset between the PPS and SHM clocks is bigger than 0.5 / > > > rate the PPS samples are rejected. So if both refclocks disagree > > >

Re: [chrony-dev] PPS reference clock rejected because of high dispersion

2014-05-20 Thread Miroslav Lichvar
On Tue, May 20, 2014 at 01:51:59PM +0200, Miroslav Lichvar wrote: > On Tue, May 20, 2014 at 11:41:39AM +0200, Hattink, Tjalling [FINT] wrote: > > When the offset between the PPS and SHM clocks is bigger than 0.5 / rate > > the PPS samples are rejected. So if both refclocks disagree only the SHM > >

Re: [chrony-dev] PPS reference clock rejected because of high dispersion

2014-05-20 Thread Miroslav Lichvar
On Tue, May 20, 2014 at 11:41:39AM +0200, Hattink, Tjalling [FINT] wrote: > When the offset between the PPS and SHM clocks is bigger than 0.5 / rate > the PPS samples are rejected. So if both refclocks disagree only the SHM > will actually publish samples. This shouldn't mark the SHM refclock as >

RE: [chrony-dev] PPS reference clock rejected because of high dispersion

2014-05-20 Thread Hattink, Tjalling [FINT]
> Before chronyd could slew or step the clock to zero offset as per the > SHM refclock, the SHM and PPS refclocks could disagree and be both > marked as falsetickers unless a third source would agree with SHM. > > The lock option is meant to take the missing second of the PPS sample > from the las