close client thread fds as soon as possible and more verbose logging when shutting down the networking
don't flush changes from batched_store when closing the store while shutting down the node
when shutting down server close listening socket as soon as possible
start tracking client threads in Hashtbl when they enter the scope that can remove them from the Hashtbl too
fix too_far_i catchup argument in case of single node scenario
some small changes to the server shutdown process to prevent it from hanging
better logging and cleaner functional style when shutting down server
always flush changes to disk after catchup
some extra logging
Merge remote-tracking branch 'refs/remotes/origin/ARAKOON-416' into 1.6