> I'm thinking there were two jumps in the first little bit. Maybe 60
> seconds?
There should be something in the log file.
> Do you have a GPS clock that is prefer? Did you set the time to 2134,
> restart gpsd so it is in the wrong epoch? Then start ntpd? very repeatable
> for me. Even on
Yo Hal!
On Wed, 21 Mar 2018 20:06:06 -0700
Hal Murray wrote:
> > Here is the log:
>
> > 12-21T17:28:40 ntpd[6085]: PROTO: 0.0.0.0 0017 07 panic_stop
> > +579076096 s; set clock manually within 1000 s. 12-21T17:28:40
> > ntpd[6085]: CLOCK: Panic: offset too big: 579076096.001
>
> You only g
Yo Eric!
On Wed, 21 Mar 2018 22:08:18 -0400
"Eric S. Raymond" wrote:
> Gary E. Miller via devel :
> > I just pulled git head, same thing. So somehow -g got broken?
>
> Looks like. I recomment bisection - with an error that gross
> you shouldn't have any trouble pinning it down.
I'm not sur
e...@thyrsus.com said:
> Alas, the client tools are difficult ebnough to test-jig that I have to
> hand-test under Python 3 before releases. I have a routine for this and I
> assume Ian does as well.
How much testing do you do by hand? Is that written down anyplace? Should
it be on the relea
> Here is the log:
> 12-21T17:28:40 ntpd[6085]: PROTO: 0.0.0.0 0017 07 panic_stop +579076096 s;
> set clock manually within 1000 s.
> 12-21T17:28:40 ntpd[6085]: CLOCK: Panic: offset too big: 579076096.001
You only get one big jump with -g. Was there another jump earlier?
I looked at the code,
Gary E. Miller via devel :
> I just pulled git head, same thing. So somehow -g got broken?
Looks like. I recomment bisection - with an error that gross
you shouldn't have any trouble pinning it down.
--
http://www.catb.org/~esr/";>Eric S. Raymond
My work is funded by the Intern
Yo All!
I was just tracking down an oddity on a RasPi. Not sure the
exact order in the chain of events. But now ntpd keeps crashing.
Somehow the system time got set to 2134. That messed up the GPS
week computation in gpsd, so gpsd PPS, my 'prefer' source, is
telling ntpd it is now 2134, but al
Hal Murray via devel :
> >From packaging/packaging.txt
>
> > The shebang lines in our Python scripts point to
> > "python". Part of our standard tests check that
> > you can change that to "python3" without breaking
> > anything.
>
> What sort of testing is that? How do I run it on my setup?
A
On Tue, Mar 20, 2018 at 09:03:45PM -0700, Hal Murray via devel wrote:
> What sort of testing is that? How do I run it on my setup?
Our Gitlab CI runs the builds and all of our python tests using python3 (using
the latest python3 from docker) on every build. See
https://gitlab.com/NTPsec/ntpse
