|
|
@@ -272,6 +272,35 @@ $ curl -X POST -H "Content-Type: application/json" -d '{ "command": "config-get"
|
|
|
</para>
|
|
|
</section> <!-- end of command-config-get -->
|
|
|
|
|
|
+ <section id="command-config-reload">
|
|
|
+ <title>config-reload</title>
|
|
|
+
|
|
|
+ <para>The <emphasis>config-reload</emphasis> command instructs
|
|
|
+ Kea to load again the configuration file that was used
|
|
|
+ previously. This operation is useful if the configuration file
|
|
|
+ has been changed by some external sources. For example, a
|
|
|
+ sysadmin can tweak the configuration file and use this command
|
|
|
+ to force Kea pick up the changes.</para>
|
|
|
+
|
|
|
+ <para>Caution should be taken when mixing this with config-set
|
|
|
+ commands. Kea remembers the location of the configuration file
|
|
|
+ it was started with. This configuration can be significantly
|
|
|
+ changed using config-set command. When config-reload is issued
|
|
|
+ after config-set, Kea will attempt to reload its original
|
|
|
+ configuration from the file, possibly losing all changes
|
|
|
+ introduced using config-set or other commands.</para>
|
|
|
+
|
|
|
+ <para><emphasis>config-reload</emphasis> does not take any parameters.
|
|
|
+ An example command invocation looks like this:
|
|
|
+<screen>
|
|
|
+{
|
|
|
+ "command": "config-reload"
|
|
|
+}
|
|
|
+</screen>
|
|
|
+ </para>
|
|
|
+ </section> <!-- end of command-config-reload -->
|
|
|
+
|
|
|
+
|
|
|
<section id="command-config-test">
|
|
|
<title>config-test</title>
|
|
|
|
|
|
@@ -491,8 +520,7 @@ $ curl -X POST -H "Content-Type: application/json" -d '{ "command": "config-get"
|
|
|
command may look like this:
|
|
|
<screen>
|
|
|
{
|
|
|
- "command": "shutdown",
|
|
|
- "arguments": { }
|
|
|
+ "command": "shutdown"
|
|
|
}
|
|
|
</screen>
|
|
|
</para>
|
Tomek Mrugalski