-
Thomas Markwalder authored
Rather that stopping it explicitly, the server was relying D2ClientMgr to stop itself during its own destruction. This was falling over during process wind-down because the IfaceMgr singletone was being destroyed before the D2ClientMgr instance. The server destructor now explicitly stops the D2ClientMgr. src/bin/dhcp4/dhcp4_messages.mes added DHCP4_SRV_D2STOP_ERROR log message src/bin/dhcp4/dhcp4_srv.cc Dhcpv4Srv::stopD2() - new method stops the NCR sender, causing it to unregister its WathSocket from IfaceMgr Dhcpv4Srv::~Dhcpv4Srv() - added call to Dhcpv4Srv::stopD2() src/bin/dhcp4/tests/dhcp4_process_tests.sh.in Enabled DNS updates in the CONFIG string. This ensures the D2 client will be started during system tests
5e855328