parent
dac9775de0
commit
733b31ebbd
|
@ -17,8 +17,8 @@ name = "solana-client-demo"
|
||||||
path = "src/bin/client-demo.rs"
|
path = "src/bin/client-demo.rs"
|
||||||
|
|
||||||
[[bin]]
|
[[bin]]
|
||||||
name = "solana-testnode"
|
name = "solana-fullnode"
|
||||||
path = "src/bin/testnode.rs"
|
path = "src/bin/fullnode.rs"
|
||||||
|
|
||||||
[[bin]]
|
[[bin]]
|
||||||
name = "solana-genesis"
|
name = "solana-genesis"
|
||||||
|
|
12
README.md
12
README.md
|
@ -36,7 +36,7 @@ $ git clone https://github.com/solana-labs/solana.git
|
||||||
$ cd solana
|
$ cd solana
|
||||||
```
|
```
|
||||||
|
|
||||||
The testnode server is initialized with a ledger from stdin and
|
The fullnode server is initialized with a ledger from stdin and
|
||||||
generates new ledger entries on stdout. To create the input ledger, we'll need
|
generates new ledger entries on stdout. To create the input ledger, we'll need
|
||||||
to create *the mint* and use it to generate a *genesis ledger*. It's done in
|
to create *the mint* and use it to generate a *genesis ledger*. It's done in
|
||||||
two steps because the mint-demo.json file contains private keys that will be
|
two steps because the mint-demo.json file contains private keys that will be
|
||||||
|
@ -50,7 +50,7 @@ used later in this demo.
|
||||||
Now you can start the server:
|
Now you can start the server:
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
$ cat genesis.log | cargo run --release --bin solana-testnode > transactions0.log
|
$ cat genesis.log | cargo run --release --bin solana-fullnode > transactions0.log
|
||||||
```
|
```
|
||||||
|
|
||||||
Wait a few seconds for the server to initialize. It will print "Ready." when it's safe
|
Wait a few seconds for the server to initialize. It will print "Ready." when it's safe
|
||||||
|
@ -76,7 +76,7 @@ Now restart the server from where we left off. Pass it both the genesis ledger,
|
||||||
the transaction ledger.
|
the transaction ledger.
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
$ cat genesis.log transactions0.log | cargo run --release --bin solana-testnode > transactions1.log
|
$ cat genesis.log transactions0.log | cargo run --release --bin solana-fullnode > transactions1.log
|
||||||
```
|
```
|
||||||
|
|
||||||
Lastly, run the client demo again, and verify that all funds were spent in the
|
Lastly, run the client demo again, and verify that all funds were spent in the
|
||||||
|
@ -128,11 +128,11 @@ Debugging
|
||||||
---
|
---
|
||||||
|
|
||||||
There are some useful debug messages in the code, you can enable them on a per-module and per-level
|
There are some useful debug messages in the code, you can enable them on a per-module and per-level
|
||||||
basis with the normal RUST\_LOG environment variable. Run the testnode with this syntax:
|
basis with the normal RUST\_LOG environment variable. Run the fullnode with this syntax:
|
||||||
```bash
|
```bash
|
||||||
$ RUST_LOG=solana::streamer=debug,solana::accountant_skel=info cat genesis.log | ./target/release/solana-testnode > transactions0.log
|
$ RUST_LOG=solana::streamer=debug,solana::server=info cat genesis.log | ./target/release/solana-fullnode > transactions0.log
|
||||||
```
|
```
|
||||||
to see the debug and info sections for streamer and accountant\_skel respectively. Generally
|
to see the debug and info sections for streamer and server respectively. Generally
|
||||||
we are using debug for infrequent debug messages, trace for potentially frequent messages and
|
we are using debug for infrequent debug messages, trace for potentially frequent messages and
|
||||||
info for performance-related logging.
|
info for performance-related logging.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue