Improve clarity around changing the `-client` param

This is a small change that (IMO) makes more explicit the effect
of changing `-client` -- namely, that you'll have to provide
`-rpc-addr` to every other consul command you run.
This commit is contained in:
Ben Scofield 2014-07-02 21:21:37 +02:00
parent bc4b5ccd48
commit 3d1e09c263
1 changed files with 3 additions and 3 deletions

View File

@ -65,9 +65,9 @@ There are several important components that `consul agent` outputs:
address is used for other `consul` commands. Other Consul commands such
as `consul members` connect to a running agent and use RPC to query and
control the agent. By default, this binds only to localhost. If you
change this address or port, you'll have to specify an `-rpc-addr` to commands
such as `consul members` so they know how to talk to the agent. This is also
the address other applications can use over [RPC to control Consul](/docs/agent/rpc.html).
change this address or port, you'll have to specify an `-rpc-addr` whenever
you run commands such as `consul members` so they know how to talk to the
agent. This is also the address other applications can use over [RPC to control Consul](/docs/agent/rpc.html).
* **Cluster Addr**: This is the address and ports used for communication between
Consul agents in a cluster. Every Consul agent in a cluster does not have to