Commit 4b4fef1c authored by Per Cederqvist's avatar Per Cederqvist
Browse files

Removed the warning not to use /usr/local as the prefix. Document how

an upgrade should be made.  Document what needs to be done when
upgrading from pre-2.1.0 to 2.1.0.  The binaries are now in "sbin",
not "bin".
parent 08028b6c
......@@ -51,18 +51,13 @@ COPYING The license for lyskomd (GNU GPL).
AUTHORS List of authors.
3. Installation
===============
3. Installing or upgrading a LysKOM installation
================================================
1. Select a location where you want the LysKOM database and server
binaries to reside. We recommend something like /usr/lyskom
(the default), /usr/local/lyskom or /opt/lyskom.
WARNING: Do not use /usr/local as the prefix! lyskomd was
written with the assumption that it should have a prefix of its
own, and it creates files such as etc/pid under the prefix you
use. (Fixing this is on the TODO list.)
WARNING: Do not place the database on an NFS-mounted directory
that is mounted with "intr"! If you do, the system calls that
writes the database may return a failure and set errno to
......@@ -83,7 +78,9 @@ AUTHORS List of authors.
You can use --with-language=sv to select that a Swedish database
should be installed (if no previous database exists). By
default, an English database will be installed.
default, an English database will be installed. This only
affects the names of a few conferences and the administrator.
You can rename them manually once the server is running.
The "-C" option tells configure to cache configuration values in
config.cache. Since the lyskomd distribution uses more than one
......@@ -110,7 +107,33 @@ AUTHORS List of authors.
5. Create a user that should own the database files. This file
assumes that the user is named "lyskom".
6. As "lyskom", install it:
6. If you are upgrading, you must stop the running lyskomd, using
the installed "komrunning" program:
$ su lyskom
$ /usr/lyskom/sbin/komrunning stop
(If you are upgrading from a version older than 2.1.0, the
komrunning program will be residing in /usr/lyskom/bin.)
7. If you are upgrading from 2.0.7 or older to 2.1.0 or newer, run
these commands to adjust to the new filesystem layout (see NEWS
for a complete list of everything that changed; this only moves
the database, config file and log files from the old to the new
layout):
$ su lyskom
$ cd /usr/lyskom
$ mv etc/config etc/lyskomd.conf
$ mkdir var/lyskomd/db
$ mv db/* var/lyskomd/db/
$ rmdir db
$ mv etc/server-log var/lyskomd.log
$ mv etc/lyskomd-log var/lyskomd.stats
$ mv etc/memory-usage var/lyskomd.memory
$ cp etc/status var/lyskomd/db/status
8. As "lyskom", install it:
$ su lyskom
$ make install
......@@ -131,11 +154,16 @@ AUTHORS List of authors.
etc/aux-items.conf. It will be overwritten even if it has been
edited locally.
7. Make sure updateLysKOM is run regularly by user lyskom. The
9. If you are upgrading from 2.0.7 or older to 2.1.0 or newer you
need to update the cron entries, so that the run the binaries
from sbin instead of bin. Once that is done, you can remove the
old etc/status file.
10. Make sure updateLysKOM is run regularly by user lyskom. The
recommended way is to add a line such as this to the cron file
of the lyskom user:
0,10,20,30,40,50 * * * * /usr/lyskom/bin/updateLysKOM
0,10,20,30,40,50 * * * * /usr/lyskom/sbin/updateLysKOM
If your cron does not support per-user cron files you will have
to arrange this in some other way.
......@@ -146,16 +174,16 @@ AUTHORS List of authors.
program. Most sane cron systems does so. You may want to
create a .forward file for user "lyskom".
8. Wait for updateLysKOM to start the server, or run updateLysKOM
11. Wait for updateLysKOM to start the server, or run updateLysKOM
manually (as user "lyskom"). You are ready.
9. Read the documentation in doc/lyskomd.info, especially the
12. Read the documentation in doc/lyskomd.info, especially the
Administration chapter. It tells you how to shut down and
restart lyskomd. LysKOM needs your attention once in a while.
Here at Lysator we expunge old texts (with "dbck -g")
approximately twice a year.
10. We would like to know about where LysKOM servers are running.
13. We would like to know about where LysKOM servers are running.
If you start a server, please mail "kom@lysator.liu.se", and
tell us that you are running a server. (You are very welcome to
tell more about you, but that's not necessary).
......
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