Commit 19b2793b authored by Per Cederqvist's avatar Per Cederqvist

Updated for lyskomd 1.6.

parent df582dba
*NOTE* This document is not updated since the 1.1 release! *NOTE*
Administrating a LysKOM site Administrating a LysKOM site
============================ ============================
For lyskomd 1.6
This document is a short description of how to administrate a LysKOM This document is a short description of how to administrate a LysKOM
database on your site. database on your site.
...@@ -12,8 +12,8 @@ administrator. ...@@ -12,8 +12,8 @@ administrator.
Once the LysKOM system is running, there is not much you will have Once the LysKOM system is running, there is not much you will have
to do to keep it that way. One thing to remember is that the current to do to keep it that way. One thing to remember is that the current
release of the server (-VERSION-) has an incomplete handling of garbage release of the server has an incomplete handling of garbage collection
collection of the database. The database is split into two files, the of the database. The database is split into two files, the
information file and the text file. Newly written texts are information file and the text file. Newly written texts are
concatenated to the text file and old texts are never removed. The concatenated to the text file and old texts are never removed. The
information file contains information about conferences, users and information file contains information about conferences, users and
...@@ -29,11 +29,11 @@ is to be run on the database, the LysKOM server *must* be stopped, or ...@@ -29,11 +29,11 @@ is to be run on the database, the LysKOM server *must* be stopped, or
unrepairable damage may result. See below for a description on how to unrepairable damage may result. See below for a description on how to
stop the server. stop the server.
There is a shell script called updateLysKOM which is used to insure There is a shell script called updateLysKOM which is used to ensure
continuous operation. This script is run with certain intervals and continuous operation. This script is run with certain intervals and
if the LysKOM server has died for some reason, updateLysKOM restarts if the LysKOM server has died for some reason, updateLysKOM restarts
it. If the server is still running properly, updateLysKOM sends a it. If the server is still running properly, updateLysKOM sends a
signal (SIGUSR1) to it, which causes the server to write call signal (SIGUSR1) to it, which causes the server to write some
statistics to a file named etc/lyskomd-log in the lyskom directory. 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 Taking the server down cleanly can be done in two ways: through the
...@@ -42,6 +42,7 @@ a suitable client, or to send the signal SIGHUP to it. This will ...@@ -42,6 +42,7 @@ a suitable client, or to send the signal SIGHUP to it. This will
cause the server to save the database and close all client cause the server to save the database and close all client
connections. It will also create a file named etc/memory-usage in connections. It will also create a file named etc/memory-usage in
which the memory usage of the server is reported. There is currently which the memory usage of the server is reported. There is currently
a small memory leak in the server. We know about it, so there is no a small memory leak in the server (typically, less than 10 memory
need to send bug reports to us about that (unless you have found where blocks leaks per server run). We know about it, so there is no need
the leak is). to send bug reports to us about that (unless you have found where the
leak is).
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment