From c448c4c004aad60ba2f2ad87d86bb46caca5fcdb Mon Sep 17 00:00:00 2001 From: Tommi Virtanen Date: Tue, 20 Sep 2011 15:22:01 -0700 Subject: [PATCH] doc: Clean reStructuredText syntax. Signed-off-by: Tommi Virtanen --- doc/dev/logs.rst | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/doc/dev/logs.rst b/doc/dev/logs.rst index 9532763debf07..4480c8f6c408c 100644 --- a/doc/dev/logs.rst +++ b/doc/dev/logs.rst @@ -1,5 +1,5 @@ ============ - Debug Logs + Debug logs ============ The main debugging tool for Ceph is the dout and derr logging functions. @@ -13,9 +13,9 @@ Dout is implemented mainly in common/DoutStreambuf.cc The dout macro avoids even generating log messages which are not going to be used, by enclosing them in an "if" statement. What this means is that if you -have the debug level set at 0, and you run this code +have the debug level set at 0, and you run this code:: -``dout(20) << "myfoo() = " << myfoo() << dendl;`` + dout(20) << "myfoo() = " << myfoo() << dendl; myfoo() will not be called here. @@ -30,9 +30,8 @@ the best performance. Sometimes, enabling logging can hide race conditions and other bugs by changing the timing of events. Keep this in mind when debugging. -============ - Performance Counters -============ +Performance counters +==================== Ceph daemons use performance counters to track key statistics like number of inodes pinned. Performance counters are essentially sets of integers and floats -- 2.39.5