Commit 78f410e8 authored by Per Cederqvist's avatar Per Cederqvist
Browse files

Document new updateLysKOM behaviour.

parent 9fa8cfb8
# INSTALL -- installation instructions for the LysKOM server
#
# $Id: INSTALL,v 1.14 1994/03/06 22:36:57 ceder Exp $
# $Id: INSTALL,v 1.15 1994/04/04 18:43:36 ceder Exp $
# Copyright (C) 1991, 1993 Lysator Academic Computer Association.
#
# This file is part of the LysKOM server.
......@@ -54,10 +54,9 @@ LysKOM has been tested on the following environments:
Sun 3, SunOS 4.1.1_U1, gcc 2.5.7
Sequent Balance 8000, Dynix 3.0.14, gcc 2.4.5
* Sun Sparc, SunOS 5.3 (Solaris 2.3), gcc
* Sun Sparc, SunOS 4.x, acc
* dumle
* hilbert
* shuksan
*astmatix* Sun Sparc, SunOS 4.x, acc
*dumle* VAXstation 2000, Ultrix-32 V3.1 (Rev. 9), gcc 2.4.5
*hilbert* HP 9000/340, HP-UX 8.0, gcc 2.4.5
* rydvax?
*) Not yet tested. This is still an alpha release.
......@@ -121,8 +120,14 @@ make does not support it.
If your cron does not support per-user cron files you will have
to arrange this in some other way.
The updateLysKOM will occasionally output a message to stderr
and exit with a non-zero exit status. It expects the cron to
send a mail to a LysKOM administrator with the output from the
program. Most sane cron systems does so. You may want to
create a .forward file for user "lyskom".
7. Wait for upateLysKOM to start the server, or run updateLysKOM
manually. You are ready.
manually (as user "lyskoM"). You are ready.
8. Read the doc/ADMINISTRATION file. It tells you how to shut down
and restart lyskomd. LysKOM needs your attention once in a
......@@ -236,5 +241,6 @@ get different behavior.
This chapter is not yet written. But let it be known that although
the server can be configured to find files in various location via the
configuration file, the updateLysKOM program contains the paths
hard-coded. This might be fixed in future releases.
configuration file, the updateLysKOM program and komrunning script
contain the paths hard-coded. This might be fixed in future releases.
It *is* safe to change the prefix, though.
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