reload tunnels.cfg when changed

[majestrate]

the router should periodically check tunnels.cfg for changes and update the router to reflect these changes instead of requiring restart.

[majestrate]

I will work on this.

[anonimal]

Excellent, thanks.

This is related to #42. In theory, the router wouldn't actually be restarted: SIGHUP would simply update the variable map and call the appropriate i2p::context members functions.

I agree that we should implement this ticket but we should also try to wrap-up SIGHUP handling as well or rethink our current design all-together.

[anonimal]

Merging with #96. Closing as duplicate.