Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
connectd: log status_failed on TOR problems
This changes connectd to use `status_fail()` on TOR problems during statup instead of `err()`. Using `err()` did not write to the logfile. To find out TOR problems during startup, the user needed to stop the system daemon and call `lightningd` manually in console to see the error. `status_fail()` logs and exits, but also prints a whole stacktrace, which is a bit too much imho on config errors. But currently there is no `status_SOMETHING` method that logs, prints and exists on an error without stacktrace. Changelog-None
- Loading branch information