Closed jan-cerny closed 8 years ago
I strongly disagree. This is not a bug, this is expected behavior. Invalid config files should cause hard loud fails of the daemon so somebody actually notices them.
What we should do is catch the configparser exception and wrap it in an exception explaining that the file is invalid and you should fix it. We definitely shouldn't continue starting the daemon with invalid config.
If
/etc/oscapd/config.ini
contains some nonsense, the deamon fails to start and gives a traceback. I think we should catch the exception, add an error message into journal and continue without trying to parse the configuration file.Here is the traceback: