Resolve Data Races

[mfrey]

Multiple parts of the code are not thread-safe resulting in data races and (possible) dead locks. We should introduce proper mechanisms such as locking. While finding problematic sections in code is a cumbersome task, helgrind might be an option. However, the execution of helgrind on the testbed test routers is painfully slow.

An exemplary execution of helgrind:

valgrind --tool=helgrind ./TestbedDaemon default.conf > log_t9-203.txt 2>&1