docs: Additions to setting up a node (#846)

anza-xyz · Apr 18, 2024 · fcabbd8 · fcabbd8
1 parent 0eae6ad
commit fcabbd8
Showing 1 changed file with 11 additions and 7 deletions.
diff --git a/docs/src/operations/setup-a-validator.md b/docs/src/operations/setup-a-validator.md
@@ -384,7 +384,7 @@ su - sol
 ## Install The Solana CLI on Remote Machine
 
 Your remote machine will need the Solana cli installed to run the validator
-software. Refer again to
+software. For simplicity, install the cli with user `sol`. Refer again to
 [Solana's Install Tool](../cli/install.md#use-solanas-install-tool) or
 [build from source](../cli/install.md#build-from-source). It is best for
 operators to build from source rather than using the pre built binaries.
@@ -409,16 +409,18 @@ nano /home/sol/bin/validator.sh
 Copy and paste the following contents into `validator.sh` then save the file:
 
 ```
+#!/bin/bash
 exec agave-validator \
-    --identity validator-keypair.json \
-    --vote-account vote-account-keypair.json \
+    --identity /home/sol/validator-keypair.json \
+    --vote-account /home/sol/vote-account-keypair.json \
     --known-validator 5D1fNXzvv5NjV1ysLjirC4WY92RNsVH18vjmcszZd8on \
     --known-validator 7XSY3MrYnK8vq693Rju17bbPkCN3Z7KvvfvJx4kdrsSY \
     --known-validator Ft5fbkqNa76vnsjYNwjDZUXoTWpP7VYm3mtsaQckQADN \
     --known-validator 9QxCLckBiJc783jnMvXZubK4wH86Eqqvashtrwvcsgkv \
     --only-known-rpc \
     --log /home/sol/agave-validator.log \
     --ledger /mnt/ledger \
+    --accounts /mnt/accounts \
     --rpc-port 8899 \
     --dynamic-port-range 8000-8020 \
     --entrypoint entrypoint.testnet.solana.com:8001 \
@@ -508,10 +510,12 @@ through the validator log output.
 
 ### Solana Validators
 
-After you have verified that your validator is in gossip, you can verify that
-your validator has joined the network using the `solana validators` command. The
-command lists all validators in the network, but like before, we can `grep` the
-output for the validator we care about:
+After you have verified that your validator is in gossip, you should stake some
+SOL to your validator. Once the stake has activated (which happens at the start
+of the next epoch), you can verify that your validator is ready to be a voting
+participant of the network with the `solana validators` command. The command
+lists all validators in the network, but like before, we can `grep` the output
+for the validator we care about:
 
 ```
 solana validators | grep <pubkey>