Gary said:
> Also no way to put panicgate in the ntp.conf. At least the man page does
> not say how.
It's a flag, not a variable. -g sets it.
There are several tinker variables in this area. Details in
docs/includes/misc-options.txt
+tinker+ [+allan+ _allan_ | +dispersion+ _dispersion_ | +
Yo Hal!
On Thu, 22 Mar 2018 18:02:55 -0700
Hal Murray wrote:
> > It just marks ALL chimers and refclocks as invalid. Then hangs.
>
> Is it really hanging? This usually indicates success:
> 03-22T17:39:49 ntpd[10392]: PROTO: 204.17.205.30 901a 8a sys_peer
It might be just ntpmon hanging. W
Yo Hal!
On Thu, 22 Mar 2018 17:43:43 -0700
"Gary E. Miller via devel" wrote:
> > [Aside, the big jump stuff should log the full date. The year is
> > missing above.]
> I think esr just patched that?
The logs below confirm this is done. Nice!
> Surprise. With that, it no longer crashes.
>
> It just marks ALL chimers and refclocks as invalid. Then hangs.
Is it really hanging? This usually indicates success:
03-22T17:39:49 ntpd[10392]: PROTO: 204.17.205.30 901a 8a sys_peer
--
These are my opinions. I hate spam.
___
devel mailing li
Yo Hal!
On Thu, 22 Mar 2018 14:04:24 -0700
Hal Murray wrote:
> [Aside, the big jump stuff should log the full date. The year is
> missing above.]
I think esr just patched that?
> Would you please try it with
> tos minsane 3
> in your config file.
Surprise. With that, it no longer crashes
Gary said:
>> Was there a successful jump in the log file?
> You tell me, below is all I have for one test cycle. I have many similar
> test cycles logs.
This looks like a successful big jump to me.
12-31T16:00:24 ntpd[1931]: PROTO: 0.0.0.0 c41c 0c clock_step
+902266367.623732 s
09-10T21:01:27
Yo Hal!
On Thu, 22 Mar 2018 12:54:44 -0700
Hal Murray wrote:
> >> There should be something in the log file.
> > Yes, I already attached to log file bits. But, once again:
>
> The subject is "-g broken". Your log sample shows ntpd exiting when
> it gets a big jump. Was there previous big
Eric said:
> I've never tried do describe that kind of testing because it's not easy to
> tell people without prior experience running the clients what a success/
> failure indication looks like. Of course alarm bells would go off on a
> crash, but the most definite thing I could say otherwise is
Yo Hal!
On Wed, 21 Mar 2018 23:48:05 -0700
Hal Murray wrote:
> > I'm thinking there were two jumps in the first little bit. Maybe 60
> > seconds?
>
> There should be something in the log file.
Yes, I already attached to log file bits. But, once again:
12-21T17:39:47 ntpd[7812]: PROTO: 0.0
Hal Murray :
>
> 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?
10 matches
Mail list logo
