Paradoxically , the LCL clock is fine when there are no refclocks. That is,
when you don't need or want it.
remote refid st t when poll reach delay offset jitter
==
*127.127.1.1 .LOCL.
On 2014-07-30, Brian Inglis brian.ing...@systematicsw.ab.ca wrote:
On 2014-07-29 21:32, Paul wrote:
On Tue, Jul 29, 2014 at 10:15 PM, Brian Inglis
brian.ing...@systematicsw.ab.ca wrote:
These statuses show the same issue with local clock reach, implying if reach
stays
at zero, sync will be
William Unruh un...@invalid.ca wrote:
On 2014-07-30, Brian Inglis brian.ing...@systematicsw.ab.ca wrote:
On 2014-07-29 21:32, Paul wrote:
On Tue, Jul 29, 2014 at 10:15 PM, Brian Inglis
brian.ing...@systematicsw.ab.ca wrote:
These statuses show the same issue with local clock reach, implying
mike cook michael.c...@sfr.fr wrote:
Paradoxically , the LCL clock is fine when there are no refclocks. That is,
when you don't need or want it.
remote refid st t when poll reach delay offset jitter
Le 30 juil. 2014 à 11:00, Rob a écrit :
mike cook michael.c...@sfr.fr wrote:
Paradoxically , the LCL clock is fine when there are no refclocks. That is,
when you don't need or want it.
remote refid st t when poll reach delay offset jitter
On Wed, Jul 30, 2014 at 12:46 AM, Brian Inglis
brian.ing...@systematicsw.ab.ca wrote:
Not seen this topic mentioned in the last year or more.
See my posts about PPS is a falseticker? of Sun Jun 15 14:37:32 UTC
2014 and Wed Jun 18 20:59:03 UTC 2014 .
These statuses show the same issue with
Nick wrote:
Thanks to all the useful suggestions on here it's all working pretty well
now on Win 7 x64.
Great!
Reducing the DPC latency by setting the Win 7 power management profile
made the most difference.
I think this is some important information to keep in mind for us.
Using
On 2014-07-30, Rob nom...@example.com wrote:
William Unruh un...@invalid.ca wrote:
On 2014-07-30, Brian Inglis brian.ing...@systematicsw.ab.ca wrote:
On 2014-07-29 21:32, Paul wrote:
On Tue, Jul 29, 2014 at 10:15 PM, Brian Inglis
brian.ing...@systematicsw.ab.ca wrote:
These statuses show the
On 30/07/14 07:50, mike cook wrote:
Paradoxically , the LCL clock is fine when there are no refclocks.
That is, when you don't need or want it.
My understanding was that the original purpose of the local clock was to
cover the case when there were no NTP managed reference clocks (but
there
Rob wrote: What happened instead is that it started to drift shortly after. I
got
alerted by nagios when it was 10us off, which was within an hour or so.
That is why I added the LOCL clock and it solved that issue, but revealed
another one.
Have you tried orphan mode instead of locl?
--
David Woolley writes:
On 30/07/14 07:50, mike cook wrote:
Paradoxically , the LCL clock is fine when there are no refclocks.
That is, when you don't need or want it.
My understanding was that the original purpose of the local clock was
to cover the case when there were no NTP managed
11 matches
Mail list logo
