[deployment-guide/comm-rel: 703/727] updated log files chapter
Jaromir Hradilek
jhradile at fedoraproject.org
Tue Oct 19 13:24:54 UTC 2010
commit a708b5fda2584f03fbca2c22a467db0de9065424
Author: Martin Prpic <mprpic at redhat.com>
Date: Fri Oct 1 16:40:27 2010 +0200
updated log files chapter
en-US/Log_Files.xml | 66 +++++++++++++++++++++++---------------------------
1 files changed, 30 insertions(+), 36 deletions(-)
---
diff --git a/en-US/Log_Files.xml b/en-US/Log_Files.xml
index f1ece10..e625c2d 100644
--- a/en-US/Log_Files.xml
+++ b/en-US/Log_Files.xml
@@ -72,6 +72,12 @@
<para>
Each of these segments of the <filename>/etc/rsyslog.conf</filename> configuration file is described in the sections below.
</para>
+ <note>
+ <title>Note</title>
+ <para>
+ Any empty lines or any text following a hash sign (#) are comments and are not processed.
+ </para>
+ </note>
<section id="s2-modules">
<title>Modules</title>
<para>
@@ -116,7 +122,7 @@ $ModLoad imfile
</para>
</listitem>
<listitem>
- <para>
+ <para>go
String Generator Modules — String generator modules generate strings based on the message content and strongly cooperate with the template feature provided by <command>rsyslog</command>. For more information on templates, refer to . The name of a string generator module always starts with the <literal>sm</literal> prefix, such as <command>smfile</command>, <command>smtradfile</command>, etc.
</para>
</listitem>
@@ -136,7 +142,7 @@ $ModLoad imfile
</para>
</warning>
</section>
- <section id="bh-global-directives">
+ <section id="s2-global-directives">
<title>Global Directives</title>
<para>
Global directives specify configuration options that apply to the <systemitem class="daemon">rsyslogd</systemitem> daemon. All of the global directives must start with a dollar sign (<literal>$</literal>). Only one directive can be specified per line. The following is an example of a global directive that specifies the maximum size of the syslog message queue:</para>
@@ -150,16 +156,16 @@ $MainMsgQueueSize
A comprehensive list of all available configuration directives and their detailed description can be found in <filename>/usr/share/doc/rsyslog-4.4.2/rsyslog_conf_global.html</filename> or online at <ulink url="http://www.rsyslog.com/doc/rsyslog_conf_global.html">http://www.rsyslog.com/doc/rsyslog_conf_global.html</ulink>.
</para>
</section>
- <section id="bh-rules">
+ <section id="s2-rules">
<title>Rules</title>
<para>
- A rule specifies the cooperation of a selector with an action. To define a rule in your <filename>/etc/rsyslog.conf</filename> configuration file, define both, a selector and an action, on one line and separate them with one or more spaces or tabs.
+ A rule specifies the cooperation of a selector with an action. To define a rule in your <filename>/etc/rsyslog.conf</filename> configuration file, define both, a selector and an action, on one line and separate them with one or more spaces or tabs. For more information on selectors, refer to <xref linkend="s3-selectors"/> and for information on actions, refer to <xref linkend="s3-actions"/>.
</para>
- <itemizedlist>
- <listitem>
- <para>
- Selectors — Selectors filter syslog messages based on two conditions: facility and priority. The following is an example of a selector:
- </para>
+ <section id="s3-selectors">
+ <title>Selectors</title>
+ <para>
+ Selectors filter syslog messages based on two conditions: facility and priority. The following is an example of a selector:
+ </para>
<screen>
<replaceable><FACILITY></replaceable>.<replaceable><PRIORITY></replaceable>
</screen>
@@ -188,58 +194,43 @@ $MainMsgQueueSize
You may also define multiple facilities and priorities simply by separating them with a comma (<literal>,</literal>). To define multiple selectors on one line, separate them with a semi-colon (<literal>;</literal>).
</para>
<para>
- The following are a few examples of selectors:
+ The following are a few examples of simple selectors:
</para>
<screen>
-kern.*
+kern.* # Selects all kernel syslog messages with any priority
</screen>
- <para>
- Select all kernel syslog messages with any priority.
- </para>
<screen>
-mail.crit
+mail.crit # Selects all mail syslog messages with priority <command>crit</command> and higher.
</screen>
- <para>
- Select all mail syslog messages with priority <command>crit</command> and higher.
- </para>
<screen>
-cron.!info,!debug
+cron.!info,!debug # Selects all cron syslog messages but those with the <command>info</command> or <command>debug</command> priority.
</screen>
+ </section>
+ <section id="s3-actions">
+ <title>Actions</title>
<para>
- Select all cron messages but those with the <command>info</command> or <command>debug</command> priority.
+ Actions specify what is to be done with the messages filtered out by the defined selector.
</para>
- </listitem>
- <listitem>
- <para>
- Actions — Actions specify what is to be done with the messages filtered out by the defined selector.
- </para>
- </listitem>
- </itemizedlist>
+ </section>
</section>
- <section id="bh-templates">
+ <section id="s2-templates">
<title>Templates</title>
<para>
</para>
</section>
- <section id="bh-filter-conditions">
+ <section id="s2-filter-conditions">
<title>Filter Conditions</title>
<para>
</para>
</section>
- <section id="bh-output-channels">
+ <section id="s2-output-channels">
<title>Output Channels</title>
<para>
</para>
</section>
-<!-- <note>
- <title>Note</title>
- <para>
- Any empty lines or lines that begin with a hash sign (#) are comments and are not processed.
- </para>
- </note> -->
</section>
<section id="s1-rsyslog-performance">
<title><command>rsyslog</command> Performance</title>
@@ -639,3 +630,6 @@ compress
</section>
</section>
</chapter>
+
+
+
More information about the docs-commits
mailing list