Better error handling on intialization.

[Robert Massaioli]

What happens when we fail, on startup, to:

• Connect to the db?
• Load configuration files?
• Start up a TCP or UDP socket?

We need to handle all of these cases in a more standard and nice way so that we can give useful error messages back to the users. I suggest that I look much more into C++ exceptions and build it that way. This is a bug because currently it makes the startup process of FUPPES flaky and you can get into not very well defined states.