diff options
author | MarcoFalke <falke.marco@gmail.com> | 2019-05-13 12:45:59 -0400 |
---|---|---|
committer | MarcoFalke <falke.marco@gmail.com> | 2019-05-13 12:46:03 -0400 |
commit | 667a8617418d837092de5b37568d60b372519462 (patch) | |
tree | fd9097435db5495542d9672a2694f9070223aacc /doc | |
parent | e79bbb73e08e3f191e97d3b67a2fbb510c5545ff (diff) | |
parent | ccc27bdcd2d91fe2c023ad004019d5b970f21dbf (diff) | |
download | bitcoin-667a8617418d837092de5b37568d60b372519462.tar.xz |
Merge #14364: doc: Clarify -blocksdir usage
ccc27bdcd2 doc: Clarify -blocksdir usage (Daniel McNally)
Pull request description:
This PR attempts to clarify and correct the `-blocksdir` argument description and default value. `-blocksdir` does not refer to the full path to the actual `blocks` directory, but rather the root/parent directory which contains the `blocks` directory. Accordingly, the default value is `<datadir>` and not `<datadir>/blocks` - this behavior of defaulting to the datadir can also be seen in init.cpp:
```cpp
if (gArgs.IsArgSet("-blocksdir")) {
path = fs::system_complete(gArgs.GetArg("-blocksdir", ""));
if (!fs::is_directory(path)) {
path = "";
return path;
}
} else {
path = GetDataDir(false);
}
```
It also attempts to clarify that only the `.dat` files containing block data are impacted by `-blocksdir`, not the index files.
I believe this would close #12828.
ACKs for commit ccc27b:
hebasto:
utACK ccc27bdcd2d91fe2c023ad004019d5b970f21dbf
Tree-SHA512: 7b65f66b0579fd56e8c8cd4f9f22d6af56181817762a68deccd7fca51820ad82d9a0c48f5f1f012e746c67bcdae7af4555fad867cb620a9ca538d465c9d86c2b
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions