On Tue, Dec 18, 2018 at 02:16:16PM -0800, Hal Murray wrote:
> > --enable-lockclock wasn't set during compile, but this DID lead me to making
> > a useful discovery: refclock_local was enabled as a compile-time option,
> > probably from when I was ensuring all Gentoo-user-accessible code paths
> > c
(sending to the list because it contains the solution)
TL;DR: compiling in refclock_local, but leaving it out of config disables sync
On Tue, Dec 18, 2018 at 01:08:27AM -0800, Hal Murray wrote:
>
> Thanks. I don't see anything fishy in the syslogs. (but still looking)
>
> How long have you wai
On Tue, Dec 18, 2018 at 12:10:07AM -0800, Hal Murray wrote:
>
> devel@ntpsec.org said:
> > 1. ntpdig localhost always gets KOD
> > 2. ntpsec never gets syncronized state: ntpwait never gives success
> > 3. local clock ends up drifting :-(
> The ntpq printout looks sane. The "*" in front of SHM(1
devel@ntpsec.org said:
> 1. ntpdig localhost always gets KOD
> 2. ntpsec never gets syncronized state: ntpwait never gives success
> 3. local clock ends up drifting :-(
The ntpq printout looks sane. The "*" in front of SHM(1) usually indicates
that it is happy.
Please try grepping for ntpd i
