1
0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-12-22 17:34:18 +03:00

docs: stop using syntax highlighting for man page code blocks

Some versions of the rst2man convertor are buggy failing to
cope with syntax highlighting in code blocks.

This isn't something we really need for the man page code
blocks, so we can just delete the highlighting directive.

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
This commit is contained in:
Daniel P. Berrangé 2019-12-11 18:05:37 +00:00
parent 766c8ae963
commit 572ce352da
6 changed files with 320 additions and 320 deletions

View File

@ -199,7 +199,7 @@ EXAMPLES
To retrieve the version of libvirtd:
.. code-block:: shell
.. code-block::
# libvirtd --version
libvirtd (libvirt) 0.8.2
@ -207,7 +207,7 @@ To retrieve the version of libvirtd:
To start libvirtd, instructing it to daemonize and create a PID file:
.. code-block:: shell
.. code-block::
# libvirtd -d
# ls -la RUNSTATEDIR/libvirtd.pid

File diff suppressed because it is too large Load Diff

View File

@ -28,7 +28,7 @@ as for monitoring and managing all clients connected to the daemon.
The basic structure of most virt-admin usage is:
.. code-block:: shell
.. code-block::
virt-admin [OPTION]... <command> [ARG]...
@ -107,7 +107,7 @@ help
**Syntax:**
.. code-block:: shell
.. code-block::
help [command-or-group]
@ -124,7 +124,7 @@ quit, exit
**Syntax:**
.. code-block:: shell
.. code-block::
quit
exit
@ -136,7 +136,7 @@ version
**Syntax:**
.. code-block:: shell
.. code-block::
version
@ -146,7 +146,7 @@ the version of the daemon.
**Example:**
.. code-block:: shell
.. code-block::
$ virt-admin version
Compiled against library: libvirt 1.2.21
@ -160,7 +160,7 @@ cd
**Syntax:**
.. code-block:: shell
.. code-block::
cd [directory]
@ -175,7 +175,7 @@ pwd
**Syntax:**
.. code-block:: shell
.. code-block::
pwd
@ -187,7 +187,7 @@ connect
**Syntax:**
.. code-block:: shell
.. code-block::
connect [URI]
@ -206,7 +206,7 @@ uri
**Syntax:**
.. code-block:: shell
.. code-block::
uri
@ -230,7 +230,7 @@ server-list
**Syntax:**
.. code-block:: shell
.. code-block::
server-list
@ -243,7 +243,7 @@ daemon-log-filters
**Syntax:**
.. code-block:: shell
.. code-block::
daemon-log-filters [--filters string]
@ -264,7 +264,7 @@ space. Each filter must conform to the form described in detail by
To define a filter which suppresses all e.g. 'virObjectUnref' DEBUG
messages, use the following:
.. code-block:: shell
.. code-block::
$ virt-admin daemon-log-filters "4:util.object"
@ -277,7 +277,7 @@ daemon-log-outouts
**Syntax:**
.. code-block:: shell
.. code-block::
daemon-log-outputs [--outputs string]
@ -298,13 +298,13 @@ space. Each output must conform to the form described in detail by
To replace the current setting for logging outputs with one that writes to
a file while logging errors only, the following could be used:
.. code-block:: shell
.. code-block::
$ virt-admin daemon-log-outputs "4:file:<absolute_path_to_the_file>"
To define multiple outputs at once they need to be delimited by spaces:
.. code-block:: shell
.. code-block::
$ virt-admin daemon-log-outputs "4:stderr 2:syslog:<msg_ident>"
@ -320,7 +320,7 @@ server-threadpool-info
**Syntax:**
.. code-block:: shell
.. code-block::
server-threadpool-info server
@ -355,7 +355,7 @@ that, unlike tasks carried out by normal workers, are within libvirt's full
control and libvirt guarantees that such a task cannot hang, thus will always
finish. An example of such a task this would be destroying a domain:
.. code-block:: shell
.. code-block::
$ virsh destroy <domain>.
@ -365,7 +365,7 @@ server-threadpool-set
**Syntax:**
.. code-block:: shell
.. code-block::
server-threadpool-set server [--min-workers count] [--max-workers count] [--priority-workers count]
@ -394,7 +394,7 @@ server-clients-info
**Syntax:**
.. code-block:: shell
.. code-block::
server-clients-info server
@ -407,7 +407,7 @@ runtime values, more specifically, the current number of clients connected to
**Example:**
.. code-block:: shell
.. code-block::
# virt-admin server-clients-info libvirtd
nclients_max : 120
@ -421,7 +421,7 @@ server-clients-set
**Syntax:**
.. code-block:: shell
.. code-block::
server-clients-set server [--max-clients count] [--max-unauth-clients count]
@ -457,7 +457,7 @@ client-list
**Syntax:**
.. code-block:: shell
.. code-block::
client-list server
@ -471,7 +471,7 @@ client-info
**Syntax:**
.. code-block:: shell
.. code-block::
client-info server client
@ -487,7 +487,7 @@ enabled within daemon).
**Examples:**
.. code-block:: shell
.. code-block::
# virt-admin client-info libvirtd 1
id : 1
@ -513,7 +513,7 @@ client-disconnect
**Syntax:**
.. code-block:: shell
.. code-block::
client-disconnect server client

View File

@ -29,7 +29,7 @@ configured in ``/etc/libvirt/virt-login-shell.conf``.
The basic structure of most ``virt-login-shell`` usage is:
.. code-block:: shell
.. code-block::
virt-login-shell

View File

@ -120,14 +120,14 @@ EXAMPLES
To retrieve the version of ``virtlockd``:
.. code-block:: shell
.. code-block::
# virtlockd --version
virtlockd (libvirt) 1.1.1
To start ``virtlockd``, instructing it to daemonize and create a PID file:
.. code-block:: shell
.. code-block::
# virtlockd -d
# ls -la RUNSTATEDIR/virtlockd.pid

View File

@ -121,14 +121,14 @@ EXAMPLES
To retrieve the version of ``virtlogd``:
.. code-block:: shell
.. code-block::
# virtlogd --version
virtlogd (libvirt) 1.1.1
To start ``virtlogd``, instructing it to daemonize and create a PID file:
.. code-block:: shell
.. code-block::
# virtlogd -d
# ls -la RUNSTATEDIR/virtlogd.pid