Wed Jun 27 10:56:13 PDT 2007
- Previous message: [Slony1-commit] slony1-engine/src/slon confoptions.c dbutils.c local_listen.c remote_listen.c remote_worker.c slon.c sync_thread.c
- Next message: [Slony1-commit] slony1-engine/src/xxid xxid.v74.sql
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Update of /home/cvsd/slony1/slony1-engine/doc/adminguide In directory main.slony.info:/tmp/cvs-serv11788 Modified Files: loganalysis.sgml slon.sgml slonconf.sgml slonik_ref.sgml Log Message: Update admin guide docs to reflect changes in logging in Slony-I 2.0 in that "interesting" messages have gotten promoted to INFO/CONFIG so that users could run slon at "-d 0" and get meaningful logs. Index: slon.sgml =================================================================== RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/slon.sgml,v retrieving revision 1.30 retrieving revision 1.31 diff -C2 -d -r1.30 -r1.31 *** slon.sgml 2 Jan 2007 20:16:58 -0000 1.30 --- slon.sgml 27 Jun 2007 17:56:11 -0000 1.31 *************** *** 64,71 **** <para> The first five non-debugging log levels (from Fatal to ! Info) are <emphasis>always</emphasis> 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> --- 64,74 ---- <para> The first five non-debugging log levels (from Fatal to ! Info) are <emphasis>always</emphasis> displayed in the logs. In ! early versions of &slony1;, the <quote>suggested</quote> ! <envar>log_level</envar> value was 2, which would list output at ! all levels down to debugging level 2. In &slony1; version 2, it ! is recommended to set <envar>log_level</envar> to 0; most of the ! consistently interesting log information is generated at levels ! higher than that. </para> </listitem> Index: slonconf.sgml =================================================================== RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/slonconf.sgml,v retrieving revision 1.16 retrieving revision 1.17 diff -C2 -d -r1.16 -r1.17 *** slonconf.sgml 2 Feb 2007 20:24:16 -0000 1.16 --- slonconf.sgml 27 Jun 2007 17:56:11 -0000 1.17 *************** *** 87,96 **** </indexterm> <listitem> ! <para>Debug log level (higher value ==> more output). Range: [0,4], default 2</para> <para> There are <link linkend="nineloglevels">nine log ! message types</link>; using this option, some or all of ! the <quote>debugging</quote> levels may be left out of the ! slon logs. </para> </listitem> --- 87,101 ---- </indexterm> <listitem> ! <para>Debug log level (higher value ==> more output). Range: [0,4], default 0</para> <para> There are <link linkend="nineloglevels">nine log ! message types</link>; using this option, some or all of the ! <quote>debugging</quote> levels may be left out of the slon ! logs. In &slony1; version 2, a lot of log message levels have ! been revised in an attempt to ensure the <quote>interesting ! stuff</quote> comes in at CONFIG/INFO levels, so that you ! could run at level 0, omitting all of the <quote>DEBUG</quote> ! messages, and still have meaningful contents in the ! logs. </para> </listitem> Index: slonik_ref.sgml =================================================================== RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/slonik_ref.sgml,v retrieving revision 1.71 retrieving revision 1.72 diff -C2 -d -r1.71 -r1.72 *** slonik_ref.sgml 22 Jun 2007 16:15:57 -0000 1.71 --- slonik_ref.sgml 27 Jun 2007 17:56:11 -0000 1.72 *************** *** 2396,2400 **** instead of <command>FAILOVER</command>, if at all possible, as <command>FAILOVER</command> winds up discarding the old origin ! node as being corrupted.</para> <para> Note that this is a &rlocking; operation, which means that --- 2396,2402 ---- instead of <command>FAILOVER</command>, if at all possible, as <command>FAILOVER</command> winds up discarding the old origin ! node as being corrupted. Before <commadand>MOVE SET</command> will ! function a <command>LOCK SET</command> is needed. ! </para> <para> Note that this is a &rlocking; operation, which means that *************** *** 2422,2425 **** --- 2424,2431 ---- <refsect1><title>Example</title> <programlisting> + LOCK SET ( + ID = 1, + ORIGIN = 1 + ); MOVE SET ( ID = 1, Index: loganalysis.sgml =================================================================== RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/loganalysis.sgml,v retrieving revision 1.9 retrieving revision 1.10 diff -C2 -d -r1.9 -r1.10 *** loganalysis.sgml 11 Jun 2007 16:02:50 -0000 1.9 --- loganalysis.sgml 27 Jun 2007 17:56:11 -0000 1.10 *************** *** 26,33 **** </screen></para></sect2> <sect2><title>DEBUG Notices</title> ! <para>Debug notices are always prefaced by the name of the thread that ! the notice originates from. You will see messages from the following threads: --- 26,48 ---- </screen></para></sect2> + <sect2><title>INFO notices</title> + + <para> Events that take place that seem like they will generally be of + interest are recorded at the INFO level, and, just as with CONFIG + notices, are always listed. </para> + + </sect2> + <sect2><title>DEBUG Notices</title> ! <para>Debug notices are of less interest, and will quite likely only ! need to be shown if you are running into some problem with &slony1;.</para> ! ! </sect2> ! ! <sect2><title>Thread name </title> ! ! <para> Notices are always prefaced by the name of the thread from ! which the notice originates. You will see messages from the following threads: *************** *** 60,68 **** </para> ! <para> How much information they display is controlled by ! the <envar>log_level</envar> &lslon; parameter; ! ERROR/WARN/CONFIG/INFO messages will always be displayed, while ! choosing increasing values from 1 to 4 will lead to additional DEBUG ! level messages being displayed. </para> </sect2> --- 75,83 ---- </para> ! <para> How much information they display is controlled by the ! <envar>log_level</envar> &lslon; parameter; ERROR/WARN/CONFIG/INFO ! messages will always be displayed, while choosing increasing values ! from 1 to 4 will lead to additional DEBUG level messages being ! displayed. </para> </sect2> *************** *** 177,185 **** <para> This section lists numerous of the error messages found in &slony1;, along with a brief explanation of implications. It is a ! fairly well comprehensive list, leaving out mostly some of ! the <command>DEBUG4</command> messages that are generally uninteresting.</para> ! <sect3 id="logshiplog"><title> Log Messages Associated with Log Shipping </title> <para> Most of these represent errors that come up if --- 192,201 ---- <para> This section lists numerous of the error messages found in &slony1;, along with a brief explanation of implications. It is a ! fairly comprehensive list, only leaving out some of the ! <command>DEBUG4</command> messages that are almost always uninteresting.</para> ! <sect3 id="logshiplog"><title> Log Messages Associated with Log ! Shipping </title> <para> Most of these represent errors that come up if
- Previous message: [Slony1-commit] slony1-engine/src/slon confoptions.c dbutils.c local_listen.c remote_listen.c remote_worker.c slon.c sync_thread.c
- Next message: [Slony1-commit] slony1-engine/src/xxid xxid.v74.sql
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list