[PATCH v2 1/3] docs: daemons: Add section on figuring out whether modular or monolithic daemon is in use

[Erik Skultety]

On Thu, Jan 20, 2022 at 04:34:01PM +0100, Peter Krempa wrote:
> Since we are at a transition period where some users may be running
> monolithic libvirtd and others already the modular topology we need a
> section that allows users to figure out which is in use.
> 
> This will be particularly important in the document about enabling
> logging, as the active log file depends on which daemon is in use.
> 
> Signed-off-by: Peter Krempa <pkrempa at redhat.com>
> ---
>  docs/daemons.rst | 52 ++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 52 insertions(+)
> 
> diff --git a/docs/daemons.rst b/docs/daemons.rst
> index 1f9bc34260..c3970eb89c 100644
> --- a/docs/daemons.rst
> +++ b/docs/daemons.rst
> @@ -435,6 +435,58 @@ host first.
>        $ systemctl enable virtproxyd-tls.socket
>        $ systemctl start virtproxyd-tls.socket
> 
> +Checking whether modular/monolithic mode is in use
> +==================================================
> +
> +New distributions are likely to use the modular mode although the upgrade
> +process preserves whichever mode was in use before the upgrade.
> +
> +To determine whether modular or monolithic mode is in use on a host running
> +``systemd`` as the init system you can take the following steps:
> +
> +#. Check whether the modular daemon infrastructure is in use
> +
> +   First check whether the modular daemon you are interested (see
> +   `Modular driver daemons`_ for a summary of which daemons are provided by
> +   libvirt) in is running:
> +
> +   #. Check ``.socket`` for socket activated services
> +
> +     ::
> +
> +       # systemctl is-active virtqemud.socket
> +       active
> +
> +   #. Check ``.service`` for always-running daemons

For ^these 2 checks, simple bulleted list would do even better. Also, for some
reason ^this hunk resulted in:

    1. Check ``.socket``...
    1. Check ``.service``...

> +
> +     ::
> +
> +       # systemctl is-active virtqemud.service
> +       active
> +
> +   If either of the above is ``active`` your system is using the modular daemons.
> +
> +#. Check whether the monolithic daemon is in use
> +
> +   #. Check ``libvirtd.socket``
> +
> +     ::
> +
> +       # systemctl is-active libvirtd.socket
> +       active
> +
> +   #. Check ``libvirtd.service`` for always-running daemon

...same ^here as above :)

with bulleted lists:
Reviewed-by: Erik Skultety <eskultet at redhat.com>