Re: Testing, 1.0, startup time

2017-08-09 Thread Eric S. Raymond via devel
Hal Murray : > One of the things we need to verify is that our code starts as fast as ntp > clsssic. I think they get going in 11 seconds. It's on their web someplace. > > I don't know how to easily automate that. A hack to scan log files might > help. Watching ntpmon, timing it to see when

Re: Time to plan for 1.0

2017-08-09 Thread Ian Bruene via devel
On 08/09/2017 01:13 AM, Gary E. Miller via devel wrote: I find leaving ntpmon running is smoking out a bunch of hard failure. In hindsight (yeah) we should have thought of this - *I* should have thought of this - a long time ago. -- In the end; what separates a Man, from a Slave? Money? Po

Re: Testing, 1.0, startup time

2017-08-09 Thread Hal Murray via devel
> I seem to recall that you were worried about your > DNS-lookup changes slowing startup. Were you able to > put that concern to rest? I've assumed that any concerns about fast startup would avoid DNS. We should compare new DNS, old DNS, and ntp classic with DNS. -- These are my opinions. I h

Re: Time to plan for 1.0

2017-08-09 Thread Gary E. Miller via devel
Yo Ian! On Wed, 9 Aug 2017 06:34:17 -0500 Ian Bruene via devel wrote: > On 08/09/2017 01:13 AM, Gary E. Miller via devel wrote: > > I find leaving ntpmon running is smoking out a bunch of hard > > failure. > > In hindsight (yeah) we should have thought of this We did, issue #341 is two month