summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorSimon MacMullen <simon@rabbitmq.com>2012-04-19 14:07:20 +0100
committerSimon MacMullen <simon@rabbitmq.com>2012-04-19 14:07:20 +0100
commit38c936a7ee2a179592a0e991885858e887df8327 (patch)
tree2b180fa3d50f046afc2e455e8291859cf075cfe1 /docs
parentb4c15dffdfb76eb8254b78f53836e5b777d3b542 (diff)
downloadrabbitmq-server-git-38c936a7ee2a179592a0e991885858e887df8327.tar.gz
s/app_name/component/g
Diffstat (limited to 'docs')
-rw-r--r--docs/rabbitmqctl.1.xml20
1 files changed, 10 insertions, 10 deletions
diff --git a/docs/rabbitmqctl.1.xml b/docs/rabbitmqctl.1.xml
index 7c74f20d47..1effd691bd 100644
--- a/docs/rabbitmqctl.1.xml
+++ b/docs/rabbitmqctl.1.xml
@@ -750,24 +750,24 @@
Certain features of RabbitMQ (such as the federation plugin)
are controlled by dynamic,
cluster-wide <emphasis>parameters</emphasis>. Each parameter
- consists of an application name, a key and a value. The
- application name and key are strings, and the value is an
+ consists of a component name, a key and a value. The
+ component name and key are strings, and the value is an
Erlang term. Parameters can be set, cleared and listed. In
general you should refer to the documentation for the feature
in question to see how to set parameters.
</para>
<variablelist>
<varlistentry>
- <term><cmdsynopsis><command>set_parameter</command> <arg choice="req"><replaceable>app_name</replaceable></arg> <arg choice="req"><replaceable>key</replaceable></arg> <arg choice="req"><replaceable>value</replaceable></arg></cmdsynopsis></term>
+ <term><cmdsynopsis><command>set_parameter</command> <arg choice="req"><replaceable>component_name</replaceable></arg> <arg choice="req"><replaceable>key</replaceable></arg> <arg choice="req"><replaceable>value</replaceable></arg></cmdsynopsis></term>
<listitem>
<para>
Sets a parameter.
</para>
<variablelist>
<varlistentry>
- <term>app_name</term>
+ <term>component_name</term>
<listitem><para>
- The name of the application for which the
+ The name of the component for which the
parameter is being set.
</para></listitem>
</varlistentry>
@@ -789,21 +789,21 @@
<para role="example-prefix">For example:</para>
<screen role="example">rabbitmqctl set_parameter federation local_username '&lt;&lt;"guest">>'</screen>
<para role="example">
- This command sets the parameter <command>local_username</command> for the <command>federation</command> application to the Erlang term <command>&lt;&lt;"guest">></command>.
+ This command sets the parameter <command>local_username</command> for the <command>federation</command> component to the Erlang term <command>&lt;&lt;"guest">></command>.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><cmdsynopsis><command>clear_parameter</command> <arg choice="req"><replaceable>app_name</replaceable></arg> <arg choice="req"><replaceable>key</replaceable></arg></cmdsynopsis></term>
+ <term><cmdsynopsis><command>clear_parameter</command> <arg choice="req"><replaceable>component_name</replaceable></arg> <arg choice="req"><replaceable>key</replaceable></arg></cmdsynopsis></term>
<listitem>
<para>
Clears a parameter.
</para>
<variablelist>
<varlistentry>
- <term>app_name</term>
+ <term>component_name</term>
<listitem><para>
- The name of the application for which the
+ The name of the component for which the
parameter is being cleared.
</para></listitem>
</varlistentry>
@@ -817,7 +817,7 @@
<para role="example-prefix">For example:</para>
<screen role="example">rabbitmqctl clear_parameter federation local_username</screen>
<para role="example">
- This command clears the parameter <command>local_username</command> for the <command>federation</command> application.
+ This command clears the parameter <command>local_username</command> for the <command>federation</command> component.
</para>
</listitem>
</varlistentry>