diff options
| author | MarcoFalke <falke.marco@gmail.com> | 2018-07-31 12:17:43 -0400 |
|---|---|---|
| committer | MarcoFalke <falke.marco@gmail.com> | 2018-07-31 12:17:55 -0400 |
| commit | 230652cafc51a087b25a5e6fbc0114e63b3be0aa (patch) | |
| tree | a9cc69b1837270f027b3620312ce7b0cbc9cc5b8 /libbitcoinconsensus.pc.in | |
| parent | 77168f766f15c6621fb2af0dfcf2dd12b971172c (diff) | |
| parent | 247d5740d29752c35861136a2fc561831c7e9832 (diff) | |
Merge #13799: Ignore unknown config file options; warn instead of error
247d5740d2 Ignore unknown config file options for now (Pieter Wuille)
04ce0d88ca Report when unknown config file options are ignored (Pieter Wuille)
Pull request description:
As reported by @satwo on IRC a few days ago, the current mechanism of treating unknown config file options as errors is problematic for options like `-rpcclienttimeout` which aren't defined for `bitcoind`.
A full solution would be to either make all binaries be aware of each other's options, or to permit config file options that only apply to specific binaries (`bitcoind`, `bitcoin-qt`, `bitcoin-cli`). Both of these seem too invasive to introduce for 0.17.
As a compromise, this PR makes it ignores those options, but still warn about it in the log file.
Tree-SHA512: dfddc771b91df3031a9c98d9f3292f8f4fcd1b97ebb7317b2f457e12d9f205dc63f42721302e7258dbb53f273d7cc041a65a0a9120972769555784e1f1cc9aef
Diffstat (limited to 'libbitcoinconsensus.pc.in')
0 files changed, 0 insertions, 0 deletions