Yo Hal! On Wed, 21 Mar 2018 20:06:06 -0700 Hal Murray <hmur...@megapathdsl.net> 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 get one big jump with -g. Was there another jump earlier? I'm thinking there were two jumps in the first little bit. Maybe 60 seconds? First ntpd decided to listen to my bad PPS, which was similar to the system time. Then it saw a cluster of servers that disagreed, and crashes. > I looked at the code, but didn't see anything fishy. It works for me: > > 20 Mar 20:02:44 ntpd[25548]: PROTO: 0.0.0.0 c41c 0c clock_step > +126316924.010938 s > 21 Mar 20:04:48 ntpd[25548]: CLOCK: time stepped by 126316924.010938 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 diffeeent NTPsc versions. > What options did you use for waf configure? bootstrap rm -R build mkdir build cd build ../configure make && make install Same as always. RGDS GARY --------------------------------------------------------------------------- Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703 g...@rellim.com Tel:+1 541 382 8588 Veritas liberabit vos. -- Quid est veritas? "If you can’t measure it, you can’t improve it." - Lord Kelvin
pgpsUYyP3fKsU.pgp
Description: OpenPGP digital signature
_______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel