This is terrible, and we should definitely recover. Its matching the previous behaviour in the library that called `log.Fatal` which logs and exits with `os.Exit(1)` just more explicit as seelog doesn't provide this (for obvious reasons!)