When using runtime setting of logging with 'virt-admin' it can be
confusing that the settings are discarded when the shutdown timeout of a
daemon is reached.
Add a note about this behaviour along with a suggestion to use
virt-admin to disable the behaviour if needed.
Signed-off-by: Peter Krempa <pkrempa(a)redhat.com>
---
docs/kbase/debuglogs.rst | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/docs/kbase/debuglogs.rst b/docs/kbase/debuglogs.rst
index 83bc0e6ad7..68b9472a83 100644
--- a/docs/kbase/debuglogs.rst
+++ b/docs/kbase/debuglogs.rst
@@ -194,6 +194,26 @@ package manager provided by your distribution to install this
package.
guideline in the sections above in place of ``virt-admin`` in the examples
below if needed.
+
+Timeout of the configured daemon
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Common deployments of libvirt start the libvirt daemons via socket activation
+and with automatic shutdown timeout of 120 seconds when no client or object is
+handled by the daemon. When a timeout is reached the daemon stops and all
+settings done during runtime via ``virt-admin`` are discarded. The daemon then
+is re-started with another command.
+
+To prevent auto-shutdown of the daemon you can use the following command::
+
+ virt-admin daemon-timeout 0
+
+The above is introduced in libvirt-8.5.0.
+
+
+Adding filters and outputs
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
The following command allows to query the list of currently active log filters:
::
--
2.36.1