several examples around on log, hooks, troubleshootings.

4 files changed, 188 insertions, 7 deletions

diff --git a/fml/doc/en/tutorial/include/chapters.ent b/fml/doc/en/tutorial/include/chapters.ent
index b809d542..574a8e58 100644
--- a/fml/doc/en/tutorial/include/chapters.ent
+++ b/fml/doc/en/tutorial/include/chapters.ent
@@ -1,5 +1,5 @@
 <!--
-   $FML: chapters.ent,v 1.8 2006/01/15 15:32:03 fukachan Exp $
+   $FML: chapters.ent,v 1.9 2006/01/16 03:21:34 fukachan Exp $
    $jaFML: chapters.ent,v 1.75 2003/06/20 22:03:12 fukachan Exp $
 -->
 
@@ -127,13 +127,11 @@
 <!entity chapter.db.modules          SYSTEM "internals/db_modules.sgml">
 <!entity chapter.dbms                SYSTEM "internals/dbms.sgml">
 <!entity chapter.hook                SYSTEM "internals/hook.sgml">
-<!entity chapter.policy              SYSTEM "policy.sgml">
-
 <!entity chapter.filename            SYSTEM "internals/filename.sgml">
-
 <!entity chapter.userctl             SYSTEM "internals/userctl.sgml">
-
 <!entity chapter.merge.internal      SYSTEM "internals/merge.sgml">
+<!entity chapter.policy              SYSTEM "policy.sgml">
+<!entity sect.hook.recipes           SYSTEM "internals/recipes.hook.sgml">
 
 
 <!-- delivery -->
@@ -192,6 +190,7 @@
 <!-- operations -->
 <!entity chapter.op.log              SYSTEM "operations/log.sgml">
 <!entity chapter.op.backup           SYSTEM "operations/backup.sgml">
+<!entity sect.op.log.recipes         SYSTEM "operations/recipes.log.sgml">
 
 
 <!-- misc -->
@@ -217,6 +216,10 @@
 
 <!-- trouble shoot -->
 <!entity chapter.troubleshoot         SYSTEM "troubleshoot/chapter.sgml">
+<!entity troubleshoot.recipes         SYSTEM "troubleshoot/recipes.sgml">
+<!entity troubleshoot.recipes.message SYSTEM "troubleshoot/recipes.message.sgml">
+
+
 <!entity recipe.version               SYSTEM "troubleshoot/recipe.version.sgml">
 <!entity recipe.listup.addresses      SYSTEM "troubleshoot/recipe.listup.addresses.sgml">
 <!entity recipe.listup.aliases        SYSTEM "troubleshoot/recipe.listup.aliases.sgml">
diff --git a/fml/doc/en/tutorial/internals/hook.sgml b/fml/doc/en/tutorial/internals/hook.sgml
index 206e4d5c..56c4f75d 100644
--- a/fml/doc/en/tutorial/internals/hook.sgml
+++ b/fml/doc/en/tutorial/internals/hook.sgml
@@ -1,5 +1,5 @@
 <!--
-   $FML: hook.sgml,v 1.1 2005/07/28 13:27:48 fukachan Exp $
+   $FML: hook.sgml,v 1.2 2005/09/28 11:05:51 fukachan Exp $
 -->
 
 
@@ -122,4 +122,16 @@ The naming convension may differ from this convension.
 </sect1>
 
 
+<sect1 id="hook.recipes">
+	<title>
+	Recipes
+	</title>
+
+<qandaset>
+&sect.hook.recipes;
+</qandaset>
+
+</sect1>
+
+
 </chapter>
diff --git a/fml/doc/en/tutorial/operations/log.sgml b/fml/doc/en/tutorial/operations/log.sgml
index fc0480c6..daf9e820 100644
--- a/fml/doc/en/tutorial/operations/log.sgml
+++ b/fml/doc/en/tutorial/operations/log.sgml
@@ -1,5 +1,5 @@
 <!--
-   $FML: log.sgml,v 1.1 2005/07/23 01:57:38 fukachan Exp $
+   $FML: log.sgml,v 1.2 2005/09/25 04:27:20 fukachan Exp $
    $jaFML: log.sgml,v 1.2 2004/10/06 09:07:41 fukachan Exp $
 -->
 
@@ -81,4 +81,14 @@ $log_computer_output_engine in config.cf file.
 </sect1>
 
 
+<sect1 id="operations.log.recipes">
+	<title>
+	Recipes
+	</title>
+
+&sect.op.log.recipes;
+
+</sect1>
+
+
 </chapter>
diff --git a/fml/doc/en/tutorial/operations/recipes.log.sgml b/fml/doc/en/tutorial/operations/recipes.log.sgml
new file mode 100644
index 00000000..758fad62
--- /dev/null
+++ b/fml/doc/en/tutorial/operations/recipes.log.sgml
@@ -0,0 +1,156 @@
+<!--
+ $FML$
+-->
+
+
+<qandaset>
+
+
+<qandaentry>
+
+<question>
+<para>
+show fml error log of yesterday.
+</para>
+</question>
+
+<answer>
+<para>
+daily.pl of &fml4; is not implemented yet.
+</para>
+
+<para>
+Currently use grep to parse the log file.
+</para>
+</answer>
+
+</qandaentry>
+
+
+<qandaentry>
+
+<question>
+<para>
+See old logs.
+</para>
+</question>
+
+<answer>
+<para>
+&fml8; appends log messages continuously into the log file at
+$ml_home_directory by default. All log messages exist in it.
+</para>
+
+<para>
+On the other hand, Unix log expires. 
+So you cannot trace too lod messages.
+</para>
+
+<para>
+Please tune parameters of expiration tools e.g. newsyslog which
+program differs from unix variants to variants to save log messages in
+at least 3 months.
+</para>
+
+</answer>
+
+</qandaentry>
+
+
+<qandaentry>
+
+<question>
+<para>
+Centralize log messages.
+</para>
+</question>
+
+<answer>
+<para>
+Unix uses syslog mechanism.
+To redirect all messages to /var/log/messages, set the following:
+<screen>
+[/etc/syslog.conf]
+
+*.*		/var/log/messages
+</screen>
+</para>
+
+<para>
+Also, &fml8; can use syslog mechanism.
+<screen>
+[/var/spool/ml/elena/config.cf]
+
+log_type	=	syslog
+</screen>
+</para>
+
+<para>
+To use these configuration, all messages are centralized to
+/var/log/messages file.
+</para>
+
+</answer>
+
+</qandaentry>
+
+
+<qandaentry>
+
+<question>
+<para>
+extract specific log messages in monitoring.
+</para>
+</question>
+
+<answer>
+<para>
+<screen>
+% tail -F /var/spool/ml/elena/log | grep 'PATTERN'
+</screen>
+
+</para>
+</answer>
+
+</qandaentry>
+
+
+<qandaentry>
+
+<question>
+<para>
+extrace the specific log messages with coping it.
+</para>
+</question>
+
+<answer>
+<para>
+
+<screen>
+% tail -F /var/spool/ml/elena/log | grep 'PATTERN' | tee FILE
+</screen>
+
+</para>
+</answer>
+
+</qandaentry>
+
+
+<qandaentry>
+
+<question>
+<para>
+Expire old log files.
+</para>
+</question>
+
+<answer>
+<para>
+Newsyslog mechanism provided by &fml4; is not implemented.
+</para>
+</answer>
+
+</qandaentry>
+
+
+</qandaset>