Date:Sat, 15 Apr 2017 02:53:23 +0200
From:Rhialto
Message-ID: <20170415005323.ga17...@falu.nl>
| I also noticed the error seems to mention IPv4 only. I am not sure if it
| managed to bind an IPv6 address on the same interface (and now it is too
| late, unfortuna
Subject: Re: bind reacts badly to dhcpcd losing/regaining connectivity
From: Robert Elz
Date: Sat, 15 Apr 2017 07:59:12 +0700
To: Rhialto
Cc: netbsd-us...@netbsd.org
Date:Sat, 15 Apr 2017 01:41:17 +0200
From:Rhialto
Message-ID: <20170414234117.ga18...@falu.nl>
|
Hal Murray :
> Thanks.
>
> >javascript 138 (0.20%) in 1 files
>
> There is a docs/asciidoc.js
> Does that mean that we also need javascript to build docs?
It's used for footnotes in the Web rendering. We don't have any footnotes.
--
http://www.catb.org/~esr/";>Eric S.
Yo Hal!
Your commit 1d40226e0f88fe91dd97f9568e07d4a0ed004dd7 broke git head.
it is mitigated in commit 12af50ead9bbf98c027a52e5921f803bf2070b7e, but
still awaiting your fix.
RGDS
GARY
---
Gary E. Miller Rellim 109 NW Wilming
Thanks.
>javascript 138 (0.20%) in 1 files
There is a docs/asciidoc.js
Does that mean that we also need javascript to build docs?
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mai
Hal Murray :
> How big is the python code?
8 KLOC. About equivalent to 3% of the fork-time volume.
> > This is significant because a "factor of four" reduction is both impressive
> > and easy for people to understand. Now we can say that.
>
> I'd call that misleading if it didn't mention the
Yo Hal!
On Fri, 14 Apr 2017 14:01:20 -0700
Hal Murray wrote:
> How big is the python code?
>
> > This is significant because a "factor of four" reduction is both
> > impressive and easy for people to understand. Now we can say
> > that.
>
> I'd call that misleading if it didn't mention the
How big is the python code?
> This is significant because a "factor of four" reduction is both impressive
> and easy for people to understand. Now we can say that.
I'd call that misleading if it didn't mention the python code.
--
These are my opinions. I hate spam.
__
Hal's async-DNS simplification finally did it. We have removed three
out of every four lines of code present at fork time.
This is significant because a "factor of four" reduction is both
impressive and easy for people to understand. Now we can say that.
--
http://www.catb.org/~esr/";>Eri
Yo Hal!
On Fri, 14 Apr 2017 11:35:28 -0700
Hal Murray wrote:
> > The switch statements we are talking about handles 'b' and 'r'
> > which are not in the option string?? What did they used to do? I
> > added the 'u'.
>
> The man page for ntp classic says they are:
Thanks.
> I assume they
Yo Hal!
On Fri, 14 Apr 2017 12:35:24 -0700
Hal Murray wrote:
> g...@rellim.com said:
> >> The default was --enable-debug. A while ago, that was changed to
> >> --disable-debug.
> > And then changed back to --enable-debug
>
> When was it changed back? I don't see that.
Covered in the git
g...@rellim.com said:
>> The default was --enable-debug. A while ago, that was changed to
>> --disable-debug.
> And then changed back to --enable-debug
When was it changed back? I don't see that.
Maybe we are having a word mixup. How about this way?
The default was DEBUG enabled. A few week
Yo Hal!
On Fri, 14 Apr 2017 11:59:56 -0700
Hal Murray wrote:
> > Then how did you last commit, which failed to build with
> > --enable-debug slip through?
>
> It used to be the default. My setup hasn't yet recovered from that
> switch.
Yeah, it will take a while for everyone to catch up.
>
g...@rellim.com said:
[Context is -b and -r on command line]
> How about I rip that cruft out then? Maybe print a message about old/unused
> option?
Probably better to print a good feature-not-supported message and crash. If
it doesn't crash, people are likely to not notice a skipping type me
> Then how did you last commit, which failed to build with --enable-debug slip
> through?
It used to be the default. My setup hasn't yet recovered from that switch.
Why didn't buildbot complain?
> I test with both (usually) before pushing.
Is that a run time test, or just a build?
We need m
Yo Hal!
On Fri, 14 Apr 2017 11:35:28 -0700
Hal Murray wrote:
> > The switch statements we are talking about handles 'b' and 'r'
> > which are not in the option string?? What did they used to do? I
> > added the 'u'.
>
> The man page for ntp classic says they are:
>
>-b, --bcastsync
> The switch statements we are talking about handles 'b' and 'r' which are not
> in the option string?? What did they used to do? I added the 'u'.
The man page for ntp classic says they are:
-b, --bcastsync
Allow us to sync to broadcast servers.
-r string, --propag
Yo Hal!
On Fri, 14 Apr 2017 02:57:07 -0700
Hal Murray wrote:
> > Warnings, not errors.
>
> Weird. I thought of that several seconds after sending the message.
A good reason not to email at 3am. :-)
> > You should only get those if you have --enable-debug
>
> That's my default setup.
T
Yo Hal!
On Fri, 14 Apr 2017 11:07:14 -0700
Hal Murray wrote:
> g...@rellim.com said:
> > Unhandled option. Looks like it has been broken a really long
> > time. I went way back and don't see it ever worked in NTPsec.
>
> It works.
How would you know? ntp:ntp is the default, right?
> The
Yo Hal!
On Fri, 14 Apr 2017 03:27:19 -0700
Hal Murray wrote:
> The default was --enable-debug. A while ago, that was changed to
> --disable-debug.
And then changed back to --enable-debug
Right now --enable-debug enables only things that developers need
or want. It enables things that are sc
g...@rellim.com said:
> Unhandled option. Looks like it has been broken a really long time. I went
> way back and don't see it ever worked in NTPsec.
It works.
There are two passes for the command line stuff. -u is handled on the other
one.
I don't know why there are two. There is a commen
Yo Hal!
On Fri, 14 Apr 2017 04:18:16 -0700
Hal Murray wrote:
> It crashes with
> Apr 14 04:00:30 fed ntpd[4726]: invalid op: 110
Great! Adding the missing default found a real bug!
That would be the second bug found in that piece of code in a month.
> 110 decimal is ascii u
Unhandled optio
Yo All!
> Build is broken this AM:
> commit 1d40226e0f88fe91dd97f9568e07d4a0ed004dd7
git head now working, I put in a partial fix until Hal can look at it:
commit bac8b43fe18a9fa09ada0e32fd2d1d31da1e1a62
To see the bug you had to use --enable-debug.
RGDS
GARY
--
Yo Hal!
Build is broken this AM:
commit 1d40226e0f88fe91dd97f9568e07d4a0ed004dd7
In file included from ../../ntpd/ntp_proto.c:7:0:
../../ntpd/ntp_proto.c:2450:27: error: 'lcladr' undeclared (first use in this
function)
current_time, latoa(lcladr), socktoa(rmtadr)));
On Fri, Apr 14, 2017 at 6:27 PM, Hal Murray wrote:
>
> We should probably measure the size difference and/or run time differences.
> The latter will take something like a busy pool server.
I have one, ntpmon.dcs1.biz , in a very busy pool, IPv6, ntpsec git head,
with gpsd git head. Debian test
It crashes with
Apr 14 04:00:30 fed ntpd[4726]: invalid op: 110
110 decimal is ascii u
This looks suspicious, but I'm sacking out.
commit d9ead3aa6abd718d4cf73bcf8023d312d510359e
Author: Gary E. Miller
Date: Thu Apr 13 18:36:24 2017 -0700
ntpd; add missing default case, fix a bad exit(
The default was --enable-debug. A while ago, that was changed to
--disable-debug.
I think we should reconsider that and/or this whole area.
There are several things all lumped together under --enable-debug and/or
--enable-debug-gdb
One is a bunch of optional compiler checking options - the s
> Warnings, not errors.
Weird. I thought of that several seconds after sending the message.
> You should only get those if you have --enable-debug
That's my default setup.
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntp
28 matches
Mail list logo
