[ntp:questions] LOCL clock reachability not 377?

William Unruh unruh at invalid.ca
Wed Jul 30 07:29:07 UTC 2014


On 2014-07-30, Brian Inglis <Brian.Inglis at SystematicSw.ab.ca> wrote:
> On 2014-07-29 21:32, Paul wrote:
>> On Tue, Jul 29, 2014 at 10:15 PM, Brian Inglis
>> <Brian.Inglis at systematicsw.ab.ca> wrote:
> These statuses show the same issue with local clock reach, implying if reach stays
> at zero, sync will be lost and PPS become a falseticker without anything to number
> seconds for too long.

Once ntpd has started using the pps clock, there is no need for anything
to number the seconds. The system itself does that perfectly fine. There
is no way that the system is going jump a second, unless it is a very
very badly broken system. Ie, one only needs something to number the
seconds at the beginning when you start up PPS. Thereafter pps on its
own is perfectly capable to maintaining the time. 

>
> Read the thread about the OP's config and problems.
>



More information about the questions mailing list