alecbcs
Improve Interface Logging
I figure it's best to make this a separate issue.
After asking for other people's thoughts, i think a good way to do logging is to either just output everything to stdout/stderr (where applicable) (probably easy to implement), or having configurable logging files per interface and maybe one for the whole daemon?
As well as having configurable logging levels: Debug (ALL the details), Info (messages that might help with troubleshooting and stuff), and Error (only actual errors).
Great! I'll start on this by adding support for the few different levels of logging to stdin/out/err over this next week and then we can start thinking about how we might support writing to a file and what effects that might have on performance.
