Tue Mar 21 08:34:06 PST 2006
- Previous message: [Slony1-general] Documentaion error for debug levle of slon command
- Next message: [Slony1-general] How to Add the Failed node back to cluster:--ERROR returned, -1 wrong database ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Melvin Davidson wrote: >The documentation for the debug option of the slon command is >misleading, or else there is a glitch in the code. > >Per the documenation: > >Options > >-ddebuglevel > The log_level specifies the level of verbosity that slon should use >when logging its activity. > The eight levels of logging are: > Error > Warn > Config > Info > Debug1 > Debug2 > Debug3 > Debug4 > >However, if you try to specify a level of Error, Warn, Config or Info, >it is not accepted as the 1st line of the log file is > >slon -dW -pslon_node_1.pid $USCUSTREP "dbname=$MASTERDBNAME >user=$REPLICATIONUSER host=$MASTERHOST port=$PGPORT" > slon1.log & >2006-03-21 11:01:01 MST WARN parameter "log_level" requires a integer >value > >Trying to specify a different level of debug will report an error also > >slon -d5 -pslon_node_1.pid $USCUSTREP "dbname=$MASTERDBNAME >user=$REPLICATIONUSER host=$MASTERHOST port=$PGPORT" > slon1.log & >2006-03-21 10:58:26 MST WARN 5 is outside the valid range for >parameter "log_level" (0 .. 4) > >So it looks like the documentation should be corrected to read as follows: > > The eight levels of logging are: > > 1 = Debug1 (Info) > 2 = Debug2 (Config) > 3.= Debug3 (Warn) > 4 = Debug4 (Error) > >Can someone please verify this for me? >TIA > > > There have been some questions about this... There *are* 8 levels; the first 4 you automatically get, in all cases. E.g. - INFO/CONFIG/WARNING/ERROR are *always* listed. The option you have is of how many of the debug levels you get; none, or up to level 4. I added this to the docs last week: ============================================================================= cbbrowne at dba2:Slony-I/slony1-HEAD-pristine/doc/adminguide> cvs diff -r1.26 slon.sgml Tuesday 16:31:04 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 -c -r1.26 -r1.27 *** slon.sgml 14 Mar 2006 18:47:23 -0000 1.26 --- slon.sgml 17 Mar 2006 18:56:26 -0000 1.27 *************** *** 1,4 **** ! <!-- $Id: slon.sgml,v 1.26 2006/03/14 18:47:23 cbbrowne Exp $ --> <refentry id="slon"> <refmeta> <refentrytitle id="app-slon-title"><application>slon</application></refentrytitle> --- 1,4 ---- ! <!-- $Id: slon.sgml,v 1.27 2006/03/17 18:56:26 cbbrowne Exp $ --> <refentry id="slon"> <refmeta> <refentrytitle id="app-slon-title"><application>slon</application></refentrytitle> *************** *** 43,50 **** <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 activity. </para> <para> --- 43,50 ---- <term><option>-d</option><replaceable class="parameter"> debuglevel</replaceable></term> <listitem> <para> ! The <envar>log_level</envar> specifies which Debug levels ! <application>slon</application> should display when logging its activity. </para> <para> *************** *** 60,65 **** --- 60,70 ---- <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-general] Documentaion error for debug levle of slon command
- Next message: [Slony1-general] How to Add the Failed node back to cluster:--ERROR returned, -1 wrong database ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list