(Parameters): Document these:

    Free space warning level
    Free space warning percent
    Free inodes warning level
    Free inodes warning percent
    Free space critical level
    Free space critical percent
    Free inodes critical level
    Free inodes critical percent
(Invoking checkkomspace): New node.

doc/lyskomd.texi

 \input texinfo
-@c $Id: lyskomd.texi,v 1.77 2003/08/29 10:39:23 ceder Exp $
+@c $Id: lyskomd.texi,v 1.78 2003/10/03 07:31:10 ceder Exp $
 @c %**start of header
 @setfilename lyskomd.info
 @include version.texi
@@ -81,6 +81,7 @@ documents version @value{VERSION} of lyskomd.
 * Running lyskomd::             How to run lyskomd.
 * Invoking updateLysKOM::       How to run updateLysKOM.
 * Invoking komrunning::         How to run komrunning.
+* Invoking checkkomspace::      How to run checkkomspace.
 * Administration::              Administering a LysKOM server.
 * Bugs::                        Known bugs in lyskomd.
 * DBCK Reference::              Checking and repairing the database.
@@ -798,6 +799,19 @@ line consisting of a single @samp{.} on standard input.
 The default is found at configure time.  The special value @samp{:}
 means that no mail will ever be sent.
 
+@item Free space warning level: @var{double}
+@itemx Free space warning percent: @var{double}
+@itemx Free inodes warning level: @var{double}
+@itemx Free inodes warning percent: @var{double}
+@itemx Free space critical level: @var{double}
+@itemx Free space critical percent: @var{double}
+@itemx Free inodes critical level: @var{double}
+@itemx Free inodes critical percent: @var{double}
+These parameters determine when the @samp{checkkomspace} progam should
+consider the space to be sufficiently large.  All levels are given in
+bytes.  Specify @samp{0} if you don't want @samp{checkkomspace} to check
+a particular limit.
+
 @end table
 
 
@@ -1199,6 +1213,33 @@ the boot sequence.
 @samp{-v} and @samp{-V} causes @code{komrunning} to report its version
 number and exit.
 
+@node Invoking checkkomspace
+@chapter Invoking checkkomspace
+
+@example
+        checkkomspace [-d] [config-file]
+        checkkomspace -h
+@end example
+
+@code{checkkomspace} checks if the partition where the database files are
+is large enough.  It is intended to be run at regular intervals from a
+management system such as Nagios.  The exit status will be 0 if all is
+OK, 1 if a warning condition exists, and 2 if an error exists.
+
+This program knows the disk usage patterns that @code{lyskomd} has, so
+it calculates the free space based on what @code{lyskomd} actually
+needs.  This might be several hundred megabytes more than what a call
+to @code{df} would report.  This also means that the result will not
+fluctuate as wildly as a @code{df} report would.
+
+@code{checkkomspace} uses the same configuration file as @code{lyskomd}
+(@pxref{Server Configuration File}).  You can specify a different
+config file via the @var{config-file} argument.
+
+@samp{-h} @code{checkkomspace} to report its version number and exit.
+
+@samp{-d} is only intended to be used by the test suite.
+
 @node Administration
 @chapter Administration