From de842f37a1d7626c6e2d334f7966d17a75c5a81f Mon Sep 17 00:00:00 2001 From: Martin Kletzander Date: Wed, 26 Oct 2022 16:19:25 +0200 Subject: [PATCH] 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 Reviewed-by: Michal Privoznik --- docs/manpages/libvirtd.rst | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/manpages/libvirtd.rst b/docs/manpages/libvirtd.rst index 1347b9b210..9a9324ffc2 100644 --- 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