Update README regarding logging.

This commit is contained in:
5chdn 2017-09-01 15:21:06 +02:00
parent fcdfae18d3
commit 05f07e85ac
No known key found for this signature in database
GPG Key ID: 1A40871B597F5F80
1 changed files with 3 additions and 5 deletions

View File

@ -158,7 +158,7 @@ It it is possible to import existing `bitcoind` database:
./target/release/pbtc import "$BITCOIND_DB/Bitcoin/blocks"
```
By default import verifies imported the blocks. You can disable this, by adding `--skip-verification flag.
By default import verifies imported the blocks. You can disable this, by adding `--skip-verification` flag.
```
./target/release/pbtc import "#BITCOIND_DB/Bitcoin/blocks" --skip-verification
@ -336,7 +336,7 @@ This is a section only for developers and power users.
You can enable detailed client logging by setting the environment variable `RUST_LOG`, e.g.,
```
RUST_LOG=verification=info ./target/release/pbtc --quiet
RUST_LOG=verification=info ./target/release/pbtc
```
`pbtc` started with this environment variable will print all logs coming from `verification` module with verbosity `info` or higher. Available log levels are:
@ -350,11 +350,9 @@ RUST_LOG=verification=info ./target/release/pbtc --quiet
It's also possible to start logging from multiple modules in the same time:
```
RUST_LOG=sync=trace,p2p=trace,verification=trace,db=trace ./target/release/pbtc --quiet
RUST_LOG=sync=trace,p2p=trace,verification=trace,db=trace ./target/release/pbtc
```
**Note:** `RUST_LOG` does only work together with command line option `--quiet` which will suppress the default `sync=info` logging.
## Internal documentation
Once released, `pbtc` documentation will be available [here][doc-url]. Meanwhile it's only possible to build it locally: