several examples around on log, hooks, troubleshootings.

2 files changed, 167 insertions, 1 deletions

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>