Updated for 1.6.1.

doc/ADMINISTRATION

 		     Administrating a LysKOM site
 		     ============================
-			   For lyskomd 1.6
+			  For lyskomd 1.6.1
 
   This document is a short description of how to administrate a LysKOM
 database on your site.
@@ -30,7 +30,7 @@ unrepairable damage may result.  See below for a description on how to
 stop the server.
 
   There is a program called updateLysKOM which is used to ensure
-continuous operation.  This script is run with certain intervals and
+continuous operation.  This program is run with certain intervals and
 if the LysKOM server has died for some reason, updateLysKOM restarts
 it.  If the server is still running properly, updateLysKOM sends a
 signal (SIGUSR1) to it, which causes the server to write some
@@ -38,22 +38,30 @@ statistics to a file named etc/lyskomd-log in the lyskom directory.
 
   Taking the server down cleanly can be done in two ways: through the
 use of the LysKOM protocol on a socket, preferably through the use of
-a suitable client, or to send the signal SIGHUP to it.  This will
+a suitable client, or by sending the signal SIGHUP to it.  This will
 cause the server to save the database and close all client
 connections.  It will also create a file named etc/memory-usage in
-which the memory usage of the server is reported.  There is currently
-a small memory leak in the server (typically, less than 10 memory
-blocks leaks per server run).  We know about it, so there is no need
-to send bug reports to us about that (unless you have found where the
-leak is).
+which the memory usage of the server is reported.
 
   To prevent updateLysKOM from restarting a server, create a file
 named /usr/lyskom/etc/status.  The file should contain a valid mail
-address on the first line.  The shell script stop_kom will create such
-a file.  UpdateLysKOM will not restart the server as long as that file
-exists.  In addition, if the file is between 1 and 2 hours old an
-email will be sent to the mail address found in the file.  If the file
-is older than that, mail will be sent to ceder. FIXME///+++<<<>>>
-
-  The shell script start_kom will remove the status file and run
-updateLysKOM.
+address on the first line.  UpdateLysKOM will not restart the server
+as long as that file exists.  In addition, if the file is between 1
+and 2 hours old an email will be sent to the mail address found in the
+file.  If the file is older than that, an error message will be
+printed on stderr and updateLysKOM will exit with a non-zero exit
+status.  cron is expected to deliver the error message to an operator.
+
+  The shell script komrunning can be used to start and stop the LysKOM
+server.  With no arguments, it will report the status.
+
+	komrunning off
+
+will shut down the server, creating the file /usr/lyskom/etc/status,
+while
+
+	komrunning on
+
+will restart it.  The actual stopping and starting of the server will
+be done by updateLysKOM the next time it is run.  komrunning only
+creates the lock file.

doc/man/lyskomd.8

-.\" $Id: lyskomd.8,v 1.12 1994/04/04 14:11:06 ceder Exp $
+.\" $Id: lyskomd.8,v 1.13 1994/04/04 18:55:08 ceder Exp $
 .\" Copyright (C) 1991, 1994  Lysator Academic Computer Association.
 .\"
 .\" This file is part of the LysKOM server.
@@ -21,8 +21,8 @@
 .\"
 .\" Please mail bug reports to bug-lyskom@lysator.liu.se. 
 .\"
-.\" $Id: lyskomd.8,v 1.12 1994/04/04 14:11:06 ceder Exp $
-.\" $Date: 1994/04/04 14:11:06 $
+.\" $Id: lyskomd.8,v 1.13 1994/04/04 18:55:08 ceder Exp $
+.\" $Date: 1994/04/04 18:55:08 $
 .TH lyskomd 8 "January 12, 1994" "Lysator"
 .SH NAME
 lyskomd - LysKOM server
@@ -34,7 +34,7 @@ lyskomd - LysKOM server
 .B config-file
 ]
 .SH DESCRIPTION
-This documents lyskomd release 1.6.  lyskomd is runs as a LysKOM server.
+This documents lyskomd release 1.6.1.  lyskomd is runs as a LysKOM server.
 .PP
 The server reads a configuration file (see CONFIGURATION below) and
 then listens for connections on the given ports (defaults are 4894