From 4055f6c074e3e1a173376845fd87212f16d850db Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Fri, 15 Jun 2018 14:39:08 -0700 Subject: [PATCH] rippled CLI - clarify --validateShards --- content/references/rippled-api/commandline-usage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/references/rippled-api/commandline-usage.md b/content/references/rippled-api/commandline-usage.md index 9e0ce17a40..d98e059b12 100644 --- a/content/references/rippled-api/commandline-usage.md +++ b/content/references/rippled-api/commandline-usage.md @@ -42,7 +42,7 @@ Daemon mode is the default mode of operation for `rippled`. In addition to the [ | `--import` | | Before fully starting, import ledger data from another `rippled` server's ledger store. Requires a valid `[import_db]` stanza in the config file. | | `--nodetoshard` | | Before fully starting, copy any complete [history shards](history-sharding.html) from the ledger store into the shard store, up to the shard store's configured maximum disk space. Uses large amounts of CPU and I/O. Caution: this command copies data (instead of moving it), so you must have enough disk space to store the data in both the shard store and the ledger store. | | `--quorum {QUORUM}` | | Override the minimum quorum for validation by requiring a agreement of `{QUORUM}` trusted validators. By default, the quorum for validation is automatically set to a safe number of trusted validators based on how many there are. This options is intended for bootstrapping [test networks](parallel-networks.html). If some validators are not online, this option can allow progress with a lower than normal quorum. **Warning:** If you set the quorum manually, it may be too low to prevent your server from diverging from the rest of the network. Only use this option if you have a deep understanding of consensus and have a need to use a non-standard configuration. | -| `---validateShards` | | Validate an existing shard store. For more information see, [History Sharding](history-sharding.html). ***TODO: This means, what, to check it for consistency? Or to consider it valid?*** | +| `---validateShards` | | Check that the data in the shard store is valid and consistent with the network history. For more information see, [History Sharding](history-sharding.html). | ## Stand-Alone Mode Options