From 58d0cf480de1df37e4aec671123768308ede790b Mon Sep 17 00:00:00 2001 From: Peter Krempa Date: Mon, 17 Jan 2022 11:55:40 +0100 Subject: [PATCH] kbase: debuglogs: Un-nest section on enabling debug logs Enabling the logs is the focus of this article. Decouple it from the first section. Signed-off-by: Peter Krempa Reviewed-by: Erik Skultety --- docs/kbase/debuglogs.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/kbase/debuglogs.rst b/docs/kbase/debuglogs.rst index 967ec10f4a..e0115bd23f 100644 --- a/docs/kbase/debuglogs.rst +++ b/docs/kbase/debuglogs.rst @@ -18,10 +18,10 @@ well. How to turn on debug logs for libvirt -------------------------------------- +===================================== Persistent setting -~~~~~~~~~~~~~~~~~~ +------------------ The daemon configuration files location is dependent on `connection URI `__. For ``qemu:///system``: @@ -71,7 +71,7 @@ However, when you are using the session mode ``qemu:///session`` or you run the ``$XDG_CONFIG_HOME/libvirt/libvirtd.conf``. Runtime setting -~~~~~~~~~~~~~~~ +--------------- Debugging anomalies can be very painful, especially when trying to reproduce it after the daemon restarts, since the new session can make the anomaly @@ -112,7 +112,7 @@ once you're finished debugging, just remember to save the original sets of filters and outputs and restore them at the end the same way as described above. Removing filters and outputs -^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +~~~~~~~~~~~~~~~~~~~~~~~~~~~~ It's also possible to remove all the filters and produce an enormous log file, but it is not recommended since some of libvirt's modules can produce a large