In a few examples we recommend disabling daemon timeout when
fetching debug logs. While it makes sense the actual syntax used
results in an error:
# virt-admin daemon-timeout 0
error: unexpected data '0'
This is because --timeout is required. Update examples to include
it.
Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com>
---
docs/kbase/debuglogs.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/kbase/debuglogs.rst b/docs/kbase/debuglogs.rst
index f08132d099..dff2cfd144 100644
--- a/docs/kbase/debuglogs.rst
+++ b/docs/kbase/debuglogs.rst
@@ -25,7 +25,7 @@ the system clears this setting::
# virt-admin -c virtqemud:///system daemon-log-outputs "3:journald
1:file:/var/log/libvirt/libvirtd.log"
# virt-admin -c virtqemud:///system daemon-log-filters "3:remote 4:event
3:util.json 3:util.object 3:util.dbus 3:util.netlink 3:node_device 3:rpc 3:access
1:*"
- # virt-admin -c virtqemud:///system daemon-timeout 0
+ # virt-admin -c virtqemud:///system daemon-timeout --timeout 0
The last command disabling timeout of the daemon is available since
``libvirt-8.6.0``. With older versions make sure to reproduce the issue within
@@ -224,7 +224,7 @@ is re-started with another command.
To prevent auto-shutdown of the daemon you can use the following command::
- virt-admin daemon-timeout 0
+ virt-admin daemon-timeout --timeout 0
The above is introduced in libvirt-8.6.0.
--
2.44.1