GitLab

to DProcessBase.

process class, D2Process, and the abstract class from which it derives,
DProcess. This class provides DHCP-DDNS specific event loop and business
logic.

The following new files have been added:

   src/bin/d2/d_process.h - defines the DProcess base class
   src/bin/d2/d2_process.h - defines the D2Process class
   src/bin/d2/d2_process.cc - implements the D2Process class
   src/bin/d2/tests/d2_process_unittests.cc - initial unit tests

Fix CSV-related test for usermanager that failed on some versions of
python (seen on 3.2.4 on Gentoo).

okayed on jabber.

one of the tests directly uses the boost mapped_file_segment class, which can
result in compiler warnings on some platforms.

accidently had phrase repeated in
c077699f

Comments, unused values, etc.

confirmed locally, and should be trivial, so I'm committing it directly.

as stopIOService public any (non templated) derived class can use it.
this seems to be the simplest and portable way to build it.

Include the stdint.h for uint64_t. It compiled on most systems, but
failed on some before.

Compensate for different error message from different versions of the
csv library. We don't really care that much about which exact text of
the error is printed as long as something is printed and makes sense. So
allow both versions know to be produced.

Don't accept invalid inputs. It seems some versions of the csv library
rejected this before, but some didn't. Making sure all of them reject
now, to get more reliable operation and consistent behavior.

Make the zone loading work even on top of MemorySegmentMapped. In
particular, handle the MemorySegmentGrown exception, which may cause
relocation of data.

this chunk was accidentally removed in e448bbba
causing test faiulres.

error_code wasn't an exception type; it should have been system_error.

ommit.

the source tree.

The create now throws on relocation, so the whole operation is tried
again. No need to worry about object being relocated.

as some compilers don't allow direct use of Base::method.

I suspect the previous version could cause the same type of use-after-free
bug, although I couldn't come up with an effective test scenario.

to enforce this style of creation, introduce a static factory method and
hide the constructor as private.