From a85a4e3db77e20ebab6b2361b6795f12d935c5e9 Mon Sep 17 00:00:00 2001 From: Zac Dover Date: Tue, 28 Nov 2023 06:08:48 +0100 Subject: [PATCH] doc/rados: improve "Ceph Subsystems" Improve the English in the subsection "Ceph Subsystems" in the section "Subsystem, Log and Debug Settings" [sic] in doc/rados/troubleshooting/log-and-debug.rst. Co-authored-by: Anthony D'Atri Signed-off-by: Zac Dover (cherry picked from commit 7bca5f57cc2c11bdd76dd0edb43c716a1d5ad355) --- doc/rados/troubleshooting/log-and-debug.rst | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/doc/rados/troubleshooting/log-and-debug.rst b/doc/rados/troubleshooting/log-and-debug.rst index 929c3f53f8841..3117541aad3cc 100644 --- a/doc/rados/troubleshooting/log-and-debug.rst +++ b/doc/rados/troubleshooting/log-and-debug.rst @@ -179,10 +179,12 @@ subsystem. Ceph's logging levels operate on a scale of ``1`` to ``20``, where logs are not sent to the output log unless one or more of the following conditions obtain: -- a fatal signal is raised or -- an ``assert`` in source code is triggered or -- upon requested. Please consult `document on admin socket - `_ for more details. +- a fatal signal has been raised or +- an assertion within Ceph code has been triggered or +- the sending of in-memory logs to the output log has been manually triggered. + Consult `the portion of the "Ceph Administration Tool documentation + that provides an example of how to submit admin socket commands + `_ for more detail. .. warning :: .. [#f1] In certain rare cases, there are logging levels that can take a value greater than 20. The resulting logs are extremely verbose. -- 2.39.5