GitLab

Also, some typos corrected.

Conflicts:
	doc/guide/bind10-guide.xml

Conflicts:
	src/bin/dhcp4/config_parser.cc
	src/bin/dhcp6/config_parser.cc
	src/lib/dhcpsrv/dhcpsrv_messages.mes
	src/lib/dhcpsrv/memfile_lease_mgr.cc

Conflicts:
	src/bin/dhcp6/tests/config_parser_unittest.cc

 commit.

This is for ticket #2501.
This is trivial and I did without review. I tested on two
systems (one with python3.3 and one without).

I didn't decide to make it open-ended at this time,
just in case we need to fix python3.4 issues first.

I decided not to add a changelog entry since was so trivial.
(Also had a workaround before by using --with-pythonpath.)

Also correct error messages in the configuration parser: the
same error is logged on any parser error, both creation and
running.  The text was made more general.

Conflicts:
	src/bin/dhcp4/config_parser.cc
	src/bin/dhcp6/config_parser.cc
	src/bin/dhcp6/dhcp6_srv.h
	src/lib/dhcpsrv/dhcpsrv_messages.mes
	src/lib/dhcpsrv/tests/Makefile.am

When the boss process was unable to connect to the msgq, it would
exit. However, it would leave the msgq process running. This patch
fixes that by killing the msgq if it is running in this case.

resolved Conflicts:
	src/lib/dns/python/Makefile.am
	src/lib/dns/python/rrset_collection_python.cc
	src/lib/dns/python/rrset_collection_python.h
	src/lib/dns/python/rrset_collection_python_inc.cc

Conflicts:
	ChangeLog
	src/bin/dhcp6/tests/dhcp6_srv_unittest.cc

The problem was, msgq started to open more file descriptors than before.
Also, the changes meant the tests didn't shut down their internal copy
of msgq properly, leaking more file descriptors.

* Do the shutdown correctly.
* Wait for msgq to terminate, so there are no race conditions between
  the old (shutting down one) and a new one for another test.
* Close all the data sockets in msgq, to prevent further leaks. The
  other ends probably still leak, but at least the threads on the other
  ends terminate on EOF, so we don't leak the threads too.
* Wait for the other threads too, so we don't spawn too many threads.
* Unrelated cleanup: remove unneeded output-suppression workaround from
  the tests, it is no longer needed.
* Unrelated cleanup: Initialize testing logger for the tests. But it
  still logs for no apparent reason, needs to be examined.