this is necessary to keep the previous behavior for FreeBSD where -Werror
is automatically disabled due to other bug of the compiler.
discussed on jabber, not seen a clear go, but I'm committing it at my
discretion to fix the buildbot errors. I've confirmed the behavior on
multiple FreeBSD boxes.
in order to keep the main configure.ac more concise, and so that we can
eventually introduce more fine-grained configuration (e.g., skipping some
checks for DNS/DHCP-only build)
At the moment, this is just a cleanup, and doesn't change the behavior itself.
the previously hardcoded zone data are mostly moved to two new files:
query_testzone_data.txt and query_testzone_data_nsec3.txt.
A new helper python script, gen-query-testdata.py, converts them into
DNS zone files and C++ files defining some C-string variables for the RRs.
The latter will be included from query_unittest.cc (instead of the hardcoded
variables).
Generated zone files are loaded via include-only zone files: example.zone
and example-nsec3.zone.
For the next step corresponding sqlite3 DB file is also generated.
Do the initialization in tests too (the executable script initializes it
only when run separately, to know the correct parameters).
Also, remove deprecated and unused auxiliary script that doesn't and
didn't work.
test parameters were adjusted accordingly.
there are some non trivial adjustments needed for the 'correct' test
cases for the original loadzone:
- completing the origin for some RDATA paramaeters (NS, SOA) does not
work yet until we complete the RDATA support. At the moment
I made them FQDNs with comments
- a few TXT data were actually incorrect in the original tests, which
caused a seeming regression. I fixed the test data.
- there was one real bug in the $INCLUDE + origin support. I'll go
fix it; right now it fails
The 'error' test cases for the original loadzone also fail, but overall
the intended behavior looked preserved. Fixing the tests to make it pass
seems to be quite difficult (because log output are different, and
the new loadzone ng is more verbose), so I plan to simply remove these
tests.
- implemented a base class Counter and a concrete XfroutCounter as an external
module under isc.statistics. Because it is easy to implement another
concrete Counter class for other module in future. The caller module can
statically import it. The new counter class provides a getter method for
each statistics item. It is intended for making loose relationship between
the counter class and the caller module.
- added implementation of unixsocket counter into the existing UnixSockServer
Class.
- added new tests for checking counters implemented in UnixSockServer are
working properly into xfrout_test.py.
- implemented enabling/disabling counting in the new counter class.
To verify and update the b10-cmdctl certificate, using a few hardcoded certificate options (cn=localhost, o=BIND10, country=US).
The tool can also be used to update the existing certificate if it has expired (it is only valid for 1 year)
Conflicts:
doc/devel/mainpage.dox
src/lib/dhcp/Makefile.am
src/lib/dhcp/lease_mgr.cc
src/lib/dhcp/lease_mgr.h
src/lib/dhcp/tests/Makefile.am
src/lib/dhcp/tests/lease_mgr_unittest.cc
A number of other files were modified to resolve incompatibilities
in the way lease managers were created, and to promote the dummy
"memfile" lease manager to a fully-fledged lease manager with
unit tests.
this works around a bit awkward installation setup where there's a link
from "python3" to "python3.x" but not from "python3-config" to the
corresponding "python3.x-config". That happens for recent versions of
Homebrew.
