diff options
| author | furszy <matiasfurszyfer@protonmail.com> | 2023-05-20 10:51:17 -0300 |
|---|---|---|
| committer | furszy <matiasfurszyfer@protonmail.com> | 2023-06-09 17:52:23 -0300 |
| commit | 3b2c61e8198bcefb1c2343caff1d705951026cc4 (patch) | |
| tree | c4ad99b748548d76a15ffaf32d9dad44c774e1ec /src/leveldb | |
| parent | 3c06926cf21dcca3074ef51506f556b2286c299b (diff) | |
| download | bitcoin-3b2c61e8198bcefb1c2343caff1d705951026cc4.tar.xz | |
Return EXIT_FAILURE on post-init fatal errors
It seems odd to return `EXIT_SUCCESS` when the node aborted
execution due a fatal internal error or any post-init problem
that triggers an unrequested shutdown.
e.g. blocks or coins db I/O errors, disconnect block failure,
failure during thread import (external blocks loading process
error), among others.
Co-authored-by: Ryan Ofsky <ryan@ofsky.org>
Diffstat (limited to 'src/leveldb')
0 files changed, 0 insertions, 0 deletions