[deployment-guide: 22/185] updated Log Files chapter

[Jaromir Hradilek]

commit cf34e5d75940773374acb5224f9fa685289bb113
Author: Martin Prpic <mprpic at redhat.com>
Date:   Thu Jan 20 14:27:27 2011 +0100

    updated Log Files chapter

 en-US/Log_Files.xml |   50 ++++++++++++++++++++++++++++++++++++++++++++++----
 1 files changed, 46 insertions(+), 4 deletions(-)
---
diff --git a/en-US/Log_Files.xml b/en-US/Log_Files.xml
index d687c0e..8e32374 100644
--- a/en-US/Log_Files.xml
+++ b/en-US/Log_Files.xml
@@ -232,6 +232,7 @@ cron.!info,!debug    # Selects all cron syslog messages except those with the <c
               <para>
                 Your specified file path can be either static or dynamic. Static files are represented by a simple file path as was shown in the example above. Dynamic files are represented by a template and a question mark (<literal>?</literal>) prefix. For more information on templates, refer to <xref linkend="s2-templates"/>.
               </para>
+              <!-- TBD: If the file you specified is a tty, special tty-handling is done, same with /dev/console. -->
             </listitem>
             </varlistentry>
             <varlistentry>
@@ -289,6 +290,36 @@ cron.!info,!debug    # Selects all cron syslog messages except those with the <c
                 </para>
               </listitem>
             </varlistentry>
+            <!--TDB
+            # Program to execute
+            # ------------------
+            *.*			^alsaunmute 	# set default volume to soundcard
+
+            <varlistentry>
+              <term>Executing programs</term>
+              <listitem>
+                <para>
+              
+                </para>
+              </listitem>
+            </varlistentry> -->
+            
+            <!--TDB in file:///usr/share/doc/rsyslog-4.6.3/rsyslog_conf_actions.html DATABASE TABLE
+            # Database action
+            # ---------------
+            # (you must have rsyslog-mysql package installed)
+            # !!! Don't forget to set permission of rsyslog.conf to 600 !!!
+            *.*	>hostname,dbname,userid,password	# (default Monitorware schema, can be created by /usr/share/doc/rsyslog-mysql-1.19.6/createDB.sql)
+
+            <varlistentry>
+              <term>Database Table</term>
+              <listitem>
+                <para>
+              
+                </para>
+              </listitem>
+            </varlistentry> -->
+            
             <varlistentry>
               <term>Discarding syslog messages</term>
               <listitem>
@@ -299,16 +330,27 @@ cron.!info,!debug    # Selects all cron syslog messages except those with the <c
               </listitem>
             </varlistentry>
           </variablelist>
-          <para>
-                 <!-- TODO: specifying multiple actions!!! -->
-          </para>
+                <para>
+                For each selector, you are allowed to specify multiple actions. To specify multiple actions for one selector, write each action on a separate line and precede it with an ampersand character (&amp;). Only the first action is allowed to have a selector specified on it's line. The following is an example of a rule with multiple actions:
+                </para>
+                <screen>
+kern.=crit joe
+&amp; /var/log/kern_crit/
+&amp; @192.168.0.1
+                </screen>
+                <para>
+                  In the example above, all kernel syslog messages with the critical priority (<parameter>crit</parameter>) are send to user <systemitem class="username">joe</systemitem>, saved in the <filename>/var/log/kern_crit/</filename> directory and forwarded to <systemitem class="ipaddress">192.168.0.1</systemitem> via the <systemitem class="protocol">UDP</systemitem> protocol.
+                </para>
+                <para>
+                  Specifying multiple actions improves the overall performance of the desired outcome since the specified selector has to be evaluated only once.
+                </para>
           <para>
             Note that any action can be followed by a template that formats the message. To specify a template, suffix an action with a semicolon (<literal>;</literal>) and specify the name of the template.
           </para>
           <warning>
             <title>Caution</title>
               <para>
-                A template must be defined before it is used in an action.
+                A template must be defined before it is used in an action, otherwise, it is ignored.
               </para>
           </warning>
           <para>