Fri Mar 17 10:56:27 PST 2006
- Previous message: [Slony1-commit] By cbbrowne: Note in slon documentation the downside to using the "lag
- Next message: [Slony1-commit] By cbbrowne: Elaborated a bit on some comments
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Log Message:
-----------
Explain logging levels (-d option) for slon a bit better
Modified Files:
--------------
slony1-engine/doc/adminguide:
slon.sgml (r1.26 -> r1.27)
-------------- next part --------------
Index: slon.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/slon.sgml,v
retrieving revision 1.26
retrieving revision 1.27
diff -Ldoc/adminguide/slon.sgml -Ldoc/adminguide/slon.sgml -u -w -r1.26 -r1.27
--- doc/adminguide/slon.sgml
+++ doc/adminguide/slon.sgml
@@ -43,8 +43,8 @@
<term><option>-d</option><replaceable class="parameter"> debuglevel</replaceable></term>
<listitem>
<para>
- The <envar>log_level</envar> specifies the level of verbosity
- that <application>slon</application> should use when logging its
+ The <envar>log_level</envar> specifies which Debug levels
+ <application>slon</application> should display when logging its
activity.
</para>
<para>
@@ -60,6 +60,11 @@
<listitem><para>Debug4</para></listitem>
</itemizedlist>
</para>
+ <para> Thus, <emphasis>all</emphasis> the non-debugging log
+ levels are always displayed in the logs. If
+ <envar>log_level</envar> is set to 2 (a routine, and, seemingly
+ preferable choice), then output at debugging levels 1 and 2 will
+ also be displayed.</para>
</listitem>
</varlistentry>
- Previous message: [Slony1-commit] By cbbrowne: Note in slon documentation the downside to using the "lag
- Next message: [Slony1-commit] By cbbrowne: Elaborated a bit on some comments
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list