docs: Remind users to remove --timeout option without socket activation

There is part of our man page that describes how to switch to the
traditional (non-socket) activation but it might still happens sometimes that
there is an extra --timeout option specified for the daemon.

Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>

diff --git a/docs/manpages/libvirtd.rst b/docs/manpages/libvirtd.rst
index 1347b9b210424055b870bb277b74d9b92aaffee7..9a9324ffc2d69f76a3ecf9c9f909692d9339341f 100644 (file)
--- a/docs/manpages/libvirtd.rst
+++ b/docs/manpages/libvirtd.rst
@@ -79,6 +79,9 @@ unit files must be masked:
    $ systemctl mask libvirtd.socket libvirtd-ro.socket \
       libvirtd-admin.socket libvirtd-tls.socket libvirtd-tcp.socket
 
+On top of that make sure that the --timeout argument is not used for the daemon
+since it would not be started upon any later connection.
+
 If using libvirt-guests service then the ordering for that service needs to be
 adapted so that it is ordered after the service unit instead of the socket unit.
 Since dependencies and ordering cannot be changed with drop-in overrides, the