Added a few test desriptions.

diff --git a/doc/manifest.xml b/doc/manifest.xml
index 5f81406..50da85b 100644 (file)
--- a/doc/manifest.xml
+++ b/doc/manifest.xml
@@ -5977,16 +5977,20 @@ similar funtions:
    </reference>
    </item>
    <item>
    </reference>
    </item>
    <item>

-   <reference href='http://logrep.sourceforge.net/'>LogRep - Logfile Extraction and Reporting
-   </reference>
+   <reference href='http://www.brains2bytes.com/alist/'>AList
+   </reference>Collect information about systems
+   </item>
+   <item>
+   <reference href='http://logrep.sourceforge.net/'>LogRep 
+   </reference> Logfile Extraction and Reporting

    </item>
    <item>
    <reference href='http://prelude-ids.org/'>Prelude Hybrid INtrusion detection system.
    </reference>
    </item>
    <item>
    </item>
    <item>
    <reference href='http://prelude-ids.org/'>Prelude Hybrid INtrusion detection system.
    </reference>
    </item>
    <item>

-   <reference href='http://www.nagios.org/'>Host and service monitoring.
-   </reference>
+   <reference href='http://www.nagios.org/'>Nagios
+   </reference> Host and service monitoring.

    </item>
 </itemize>
 </para>
    </item>
 </itemize>
 </para>

diff --git a/doc/manual.xml b/doc/manual.xml
index 26a0567..133eb68 100644 (file)
--- a/doc/manual.xml
+++ b/doc/manual.xml
@@ -6,7 +6,7 @@
 <!--
       Gnucomo - Gnu Computer Monitoring Tutorial
       Original author :  Peter Roozemaal
 <!--
       Gnucomo - Gnu Computer Monitoring Tutorial
       Original author :  Peter Roozemaal

-      Version         : $Revision: 1.5 $
+      Version         : $Revision: 1.6 $

 
       This document is prepared for XMLDoc. Transform to HTML,
       LaTeX, Postscript or plain text with XMLDoc utilities and
 
       This document is prepared for XMLDoc. Transform to HTML,
       LaTeX, Postscript or plain text with XMLDoc utilities and


@@ -852,62 +852,15 @@ However, you can not use the output from <strong>ls</strong> directly as
 input for <strong>gcm_input</strong>.
 You need to strip off two siffixes off the filenames to make it look like
 a <code>rpm -qa</code> output.
 input for <strong>gcm_input</strong>.
 You need to strip off two siffixes off the filenames to make it look like
 a <code>rpm -qa</code> output.

-The following script will do just that:
+Futhermore, a repository of updates often contains multiple versions of a package 
+file.
+You want to make sure that the latest version of each package is recorded in the
+Gnucomo database.
+The (python) script <code>report_repository.py</code> will perfom these tasks:

 </para>
 
 <verbatim>
 </para>
 
 <verbatim>

-
-#!/bin/sh
-#
-#   Turn an 'ls' listing of RPM files into an 'rpm -qa' listing
-#   Reads a list of filenames, possibly preceeded by a directory and
-#   strips the directory path from the beginning and the two suffices
-#   from the end of each filename. For example, the name
-#   "/mnt/cdrom/RedHat/RPMS/kernel-2.4.20-13.7.i686.rpm" gets turned
-#   into a simple "kernel-2.4.20-13.7".
-
-while read filename
-do
-   case $filename in
-   *.src.rpm)
-   ;;
-
-   *)
-      filename=`basename $filename .rpm`
-      case $filename in
-      *.athlon)
-         rpm=`basename $filename .athlon`
-      ;; 
-      *.i386)
-         rpm=`basename $filename .i386`
-      ;; 
-      *.i486)
-         rpm=`basename $filename .i486`
-      ;; 
-      *.i586)
-         rpm=`basename $filename .i586`
-      ;; 
-      *.i686)
-         rpm=`basename $filename .i686`
-      ;; 
-      *.noarch)
-         rpm=`basename $filename .noarch`
-      ;; 
-      esac
-      echo $rpm
-   ;;
-   esac
-done
-
-</verbatim>
-
-<para>
-Suppose this script is stored as <code>ls-rpm</code>, you can apply it
-like this:
-</para>
-
-<verbatim>
-   ls /mnt/cdrom/RedHat/RPMS | ls-rpm | sort | uniq | gcm_input -h redhat-7.3
+   python report_repository.py /mnt/cdrom/RedHat/RPMS | gcm_input -h redhat-7.3

 </verbatim>
 
 <para>
 </verbatim>
 
 <para>

diff --git a/doc/test.xml b/doc/test.xml
index fa04f23..aad6716 100644 (file)
--- a/doc/test.xml
+++ b/doc/test.xml
@@ -6,7 +6,7 @@
 <!--
       Gnucomo - Gnu Computer Monitoring Test description
       Original author :  Arjen Baart - arjen@andromeda.nl
 <!--
       Gnucomo - Gnu Computer Monitoring Test description
       Original author :  Arjen Baart - arjen@andromeda.nl

-      Version         : $Revision: 1.1 $
+      Version         : $Revision: 1.2 $

 
       This document is prepared for XMLDoc. Transform to HTML,
       LaTeX, Postscript or plain text with XMLDoc utilities and
 
       This document is prepared for XMLDoc. Transform to HTML,
       LaTeX, Postscript or plain text with XMLDoc utilities and


@@ -144,6 +144,84 @@ This tests problem report nr. 30.
 </para>
 </section>
 
 </para>
 </section>
 

+<section>
+<heading>Test 0013: RPM package updates</heading>
+<para>
+Create an object and parse an RPM package list and another RPM package
+list where some packages are upgraded and removed.
+Parameters and properties are created in the database.
+Reading the second list should lead to notifications and additional
+records in the parameter history table.
+</para>
+</section>
+
+<section>
+<heading>Test 0014: RPM package update repeats</heading>
+<para>
+Create an object and parse an RPM package list and another RPM package
+list where some packages are upgraded and removed.
+The second package list is read twice.
+Parameters and properties are created in the database.
+Reading the second list should lead to notifications and additional
+records in the parameter history table.
+Reading the second list another time should not change anything in the
+database.
+This tests PR 31.
+</para>
+</section>
+<section>
+<heading>Test 0015: Debian package list and repeated updates</heading>
+<para>
+
+ Debian package list and repeated updates
+
+This is basically the same test as test 0014, except we are now using
+a Debian list from 'dpkg -l' instead of RPM.
+Create an object and parse a Debian package list and another Debian package
+list where some packages are upgraded and removed.
+The second package list is read twice.
+Parameters and properties are created in the database.
+Reading the second list should lead to notifications and additional
+records in the parameter history table.
+Reading the second list another time should not change anything in the
+database.
+This tests PR 31.
+</para>
+
+</section>
+
+<section>
+<heading>Test 0020: Logrunner normal operation</heading>
+<para>
+Read a small logfile and check the XML output created
+by logrunner.
+Logrunner will put the hostname of the system where the test
+is run in the ouput file.
+</para>
+</section>
+
+<section>
+<heading>Test 0021: Logrunner continuation</heading>
+<para>
+Read a small logfile in two parts and check the XML output created
+by logrunner.
+After reading the log for the first time, additional content is added
+to the file and logrunner is called a second time.
+This tests whether logrunner will continue a log file after additional
+data is appended to that log file.
+</para>
+</section>
+
+<section>
+<heading>Test 0022: Logrunner long lines</heading>
+<para>
+Read a small logfile with a long (> 4096 bytes) line.
+Logrunner should create an XML message with the long
+line intact.
+Note that the line is longer than logrunner's input buffer.
+</para>
+</section>
+

 </chapter>
 
 </book>
 </chapter>
 
 </book>