2
0
mirror of https://gitlab.isc.org/isc-projects/kea synced 2025-08-30 05:27:55 +00:00

[5151] Whitespace correction

This commit is contained in:
Tomek Mrugalski 2017-03-15 17:06:27 +01:00
parent aad3f20355
commit 0975628ecc

View File

@ -45,9 +45,9 @@
{ {
"command": "foo", "command": "foo",
"arguments": { "arguments": {
"param1": "value1", "param1": "value1",
"param2": "value2", "param2": "value2",
... ...
} }
} }
</screen> </screen>
@ -64,9 +64,9 @@
"result": 0|1, "result": 0|1,
"text": "textual description", "text": "textual description",
"arguments": { "arguments": {
"argument1": "value1", "argument1": "value1",
"argument2": "value2", "argument2": "value2",
... ...
} }
} }
</screen> </screen>
@ -218,9 +218,9 @@ will be sent to Kea and the responses received from Kea printed to standard outp
<title>list-commands</title> <title>list-commands</title>
<para> <para>
The <emphasis>list-commands</emphasis> command retrieves a list of all The <emphasis>list-commands</emphasis> command retrieves a list of all
commands supported by the server. It does not take any arguments. commands supported by the server. It does not take any arguments.
An example command may look like this: An example command may look like this:
<screen> <screen>
{ {
"command": "list-commands", "command": "list-commands",
@ -229,9 +229,9 @@ will be sent to Kea and the responses received from Kea printed to standard outp
</screen> </screen>
</para> </para>
<para> <para>
The server will respond with a list of all supported commands. The The server will respond with a list of all supported commands. The
arguments element will be a list of strings. Each string will convey arguments element will be a list of strings. Each string will convey
one supported command. one supported command.
</para> </para>
</section> <!-- end of command-list-commands --> </section> <!-- end of command-list-commands -->
@ -282,7 +282,7 @@ will be sent to Kea and the responses received from Kea printed to standard outp
reload is triggered via a signal, the server will use the configuration reload is triggered via a signal, the server will use the configuration
stored in its configuration file. stored in its configuration file.
The server's response will contain a numeric code, "result" (0 for success, The server's response will contain a numeric code, "result" (0 for success,
non-zero on failure), and a string, "text", describing the outcome: non-zero on failure), and a string, "text", describing the outcome:
<screen> <screen>
{"result": 0, "text": "Configuration successful." } {"result": 0, "text": "Configuration successful." }
@ -298,10 +298,10 @@ will be sent to Kea and the responses received from Kea printed to standard outp
<title>shutdown</title> <title>shutdown</title>
<para> <para>
The <emphasis>shutdown</emphasis> command instructs the server to initiate The <emphasis>shutdown</emphasis> command instructs the server to initiate
its shutdown procedure. It is the equivalent of sending a SIGTERM signal its shutdown procedure. It is the equivalent of sending a SIGTERM signal
to the process. This command does not take any arguments. An example to the process. This command does not take any arguments. An example
command may look like this: command may look like this:
<screen> <screen>
{ {
"command": "shutdown", "command": "shutdown",
@ -310,8 +310,8 @@ will be sent to Kea and the responses received from Kea printed to standard outp
</screen> </screen>
</para> </para>
<para> <para>
The server will respond with a confirmation that the shutdown procedure The server will respond with a confirmation that the shutdown procedure
has been initiated. has been initiated.
</para> </para>
</section> <!-- end of command-shutdown --> </section> <!-- end of command-shutdown -->