Updating tribe doc to avoid port conflict

- Just adds an additional flag to instructions to prevent error from testing on the same machine
intelsdi-x · Sep 21, 2016 · 3eda2bd · 3eda2bd
1 parent 6dee889
commit 3eda2bd
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/TRIBE.md b/docs/TRIBE.md
@@ -59,7 +59,7 @@ Since tribe is implemented on top of a gossip based protocol there is no "master
 
 Start another instance of snapd to join to our existing tribe. The local IP address is 192.168.136.176 in our example. Note that we need a few more parameters to avoid conflicting ports on a single system:
 ```
-$ snapd --tribe -t 0 --tribe-port 6001 --api-port 8182 --tribe-node-name secondnodename --tribe-seed 192.168.136.176:6000
+$ snapd --tribe -t 0 --tribe-port 6001 --api-port 8182 --tribe-node-name secondnodename --tribe-seed 192.168.136.176:6000 --control-listen-port 8083
 ```
 
 Both snapd instances will see each other in their member list: