GitLab

Conflicts:
	ChangeLog
	src/bin/dhcp6/kea_controller.cc
	src/lib/dhcpsrv/daemon.h

 - ChangLog updated (b10-dhcp4 => DHCPv4 server)
 - stand-alone mode removed in Kea4,Kea6
 - getInstance() used instead of server_
 - ctrl_dhcp4_srv.cc: one stringstream instance now shared by all error messages
 - ctrl_dhcp4_srv.h: comments cleaned up
 - Added log message for received configuration
 - kea_controller.cc: Unnecessary header/using namespace removed
 - *.json files are now cleaned up in src/bin/dhcp4/tests
 - added comment that explains lack of tests for Bundy backend
 - kea_controller_unittest.cc now uses the same filename everywhere

Changes also applied to Kea6 (where applicable).

Without that change the name of the process will be truncated if the
command line to start the process is out of bounds of the window size.
When running unit tests on the build farm there is in fact no window so
the ps function wouldn't find a pid of Kea and the shell-based tests
would fail.

Implements TSIG in D2

Fixed Conflicts:
	src/bin/d2/nc_trans.cc
	src/bin/d2/nc_trans.h
	src/bin/d2/tests/nc_test_utils.cc
	src/bin/d2/tests/nc_trans_unittests.cc

Consolidated DNSClient::doUpdate variants into a single method which
accepts a smart pointer to a TSIGKey instead of TSIGKey reference.
Simplified some unit tests.
Added missing commentary.
Corrected typos and copyright dates.

exclude include/ so will remove /usr/local/include too

also add a hack to change the paths to be consistent
in the case that the directory the job is done in is a symlink
to another directory.
(Alternative method would be to run the lcov tool multiple times
for each path and set the base-directory switch plus add-tracefile
switch to combine.)

I didn't get this reviewed. I am under assuption that this make target
is rarely used.

On the FreeBSD10 system installed on the physical machine with the CPU:
(Intel(R) Core(TM) i7-2700K CPU @ 3.50GHz), Kea compiled with clang 3.3,
it takes slightly more than 2100ms (the previous timeout value) for the
callback to occur. This seems to be specific to this system but on the
other hand we don't test on FreeBSDs a lot, so the problem may be more
common than we think. This was okayed on Jabber.

The unit tests used to compare the addresses in the textual formats. Since
IPv6 addresses may be presented in various ways, it led to false
positives on some OSes.