mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-11-21 04:05:49 +00:00
update docs for pr 5225
This commit is contained in:
@@ -30,7 +30,7 @@ The `rippled` executable usually runs as a daemon that powers the XRP Ledger, al
|
|||||||
- **Other Usage** - Each of the following commands causes the `rippled` executable to print some information, then exit:
|
- **Other Usage** - Each of the following commands causes the `rippled` executable to print some information, then exit:
|
||||||
- **Help** - Use `-h` or `--help` to print a usage statement.
|
- **Help** - Use `-h` or `--help` to print a usage statement.
|
||||||
- **Unit Tests** - Use `-u` or `--unittest` to run unit tests and print a summary of results. This can be helpful to confirm that you have compiled `rippled` successfully.
|
- **Unit Tests** - Use `-u` or `--unittest` to run unit tests and print a summary of results. This can be helpful to confirm that you have compiled `rippled` successfully.
|
||||||
- **Version statement** - Use `--version` to have `rippled` print its version number, then exit.
|
- **Version statement** - Use `--version` to have `rippled` print its version number, Git commit hash, and Git build branch.
|
||||||
|
|
||||||
## Generic Options
|
## Generic Options
|
||||||
|
|
||||||
|
|||||||
@@ -85,6 +85,9 @@ The `info` object may have some arrangement of the following fields:
|
|||||||
| `build_version` | String | The version number of the running `rippled` server. |
|
| `build_version` | String | The version number of the running `rippled` server. |
|
||||||
| `closed_ledger` | Object | _(May be omitted)_ Information on the most recently closed ledger that has not been validated by consensus. If the most recently validated ledger is available, the response omits this field and includes `validated_ledger` instead. The member fields are the same as the `validated_ledger` field. |
|
| `closed_ledger` | Object | _(May be omitted)_ Information on the most recently closed ledger that has not been validated by consensus. If the most recently validated ledger is available, the response omits this field and includes `validated_ledger` instead. The member fields are the same as the `validated_ledger` field. |
|
||||||
| `complete_ledgers` | String | Range expression indicating the sequence numbers of the ledger versions the local `rippled` has in its database. This may be a disjoint sequence such as `24900901-24900984,24901116-24901158`. If the server does not have any complete ledgers (for example, it recently started syncing with the network), this is the string `empty`. |
|
| `complete_ledgers` | String | Range expression indicating the sequence numbers of the ledger versions the local `rippled` has in its database. This may be a disjoint sequence such as `24900901-24900984,24901116-24901158`. If the server does not have any complete ledgers (for example, it recently started syncing with the network), this is the string `empty`. |
|
||||||
|
| `git` | Object | _(Admin only)_ The Git details of your `rippled` build. |
|
||||||
|
| `git.branch` | String | _(Admin only)_ The Git branch used to build your version of `rippled`. |
|
||||||
|
| `git.hash` | String | _(Admin only)_ The Git hash of the commit used to build your version of `rippled`. |
|
||||||
| `hostid` | String | On an admin request, returns the hostname of the server running the `rippled` instance; otherwise, returns a single [RFC-1751][] word based on the [node public key](../../../../concepts/networks-and-servers/peer-protocol.md#node-key-pair). |
|
| `hostid` | String | On an admin request, returns the hostname of the server running the `rippled` instance; otherwise, returns a single [RFC-1751][] word based on the [node public key](../../../../concepts/networks-and-servers/peer-protocol.md#node-key-pair). |
|
||||||
| `io_latency_ms` | Number | Amount of time spent waiting for I/O operations, in milliseconds. If this number is not very, very low, then the `rippled` server is probably having serious load issues. |
|
| `io_latency_ms` | Number | Amount of time spent waiting for I/O operations, in milliseconds. If this number is not very, very low, then the `rippled` server is probably having serious load issues. |
|
||||||
| `jq_trans_overflow` | String - Number | The number of times (since starting up) that this server has had over 250 transactions waiting to be processed at once. A large number here may mean that your server is unable to handle the transaction load of the XRP Ledger network. For detailed recommendations of future-proof server specifications, see [Capacity Planning](../../../../infrastructure/installation/capacity-planning.md). |
|
| `jq_trans_overflow` | String - Number | The number of times (since starting up) that this server has had over 250 transactions waiting to be processed at once. A large number here may mean that your server is unable to handle the transaction load of the XRP Ledger network. For detailed recommendations of future-proof server specifications, see [Capacity Planning](../../../../infrastructure/installation/capacity-planning.md). |
|
||||||
|
|||||||
Reference in New Issue
Block a user