Commit e7dbc369 authored by Per Cederqvist's avatar Per Cederqvist
Browse files

Added info about tmp-limits.h.

parent 2d28fca5
#
# $Id: INSTALL,v 1.2 1991/09/15 09:53:52 linus Exp $
# $Id: INSTALL,v 1.3 1991/09/16 17:24:01 ceder Exp $
# Copyright (C) 1991 Lysator Academic Computer Association.
#
# This file is part of the LysKOM server.
......@@ -81,7 +81,7 @@ In the following, $T stands for the directory in which this file
compiler that supports prototypes. If your ranlib doesn't support
the -t flag, just omit it in the definition of TOUCHLIB. If your ld
doesn't support the -L flag take it out from LDFLAGS. See also step
6 below.
7 below.
3) Edit $T/config/$H-config.h
......@@ -117,14 +117,23 @@ In the following, $T stands for the directory in which this file
created. It can be set individually for each conference. This is
the default value.
5) Type
5) Edit src/server/tmp-limits.h
There is a hardcoded limit to the number of persons and texts that
LysKOM supports. The limit won't be hardcoded in future releases.
LysKOM currently has a table that holds as many entries as is said
here, so it is wasteful to have a too big number here. On the
other hand, you must recompile and restart the server when the
limit is reached, so it is unwise to set it too low.
6) Type
./Config $H
This takes some 1.5 minutes on a Sun 3/80.
6) If your ld supports -L, type
7) If your ld supports -L, type
./Build
......@@ -147,9 +156,9 @@ In the following, $T stands for the directory in which this file
All binaries should now be built.
7) Ask root to create a user `lyskom' (or a name of your choice).
8) Ask root to create a user `lyskom' (or a name of your choice).
8) Create the directory that you specified as DEFAULT_DBASE_DIR in
9) Create the directory that you specified as DEFAULT_DBASE_DIR in
step 4. Recursively copy the contents of $T/db-crypt into
DEFAULT_DBASE_DIR/db: (The remainder of this file assumes that
DEFAULT_DBASE_DIR is /usr/lyskom).
......@@ -171,7 +180,7 @@ In the following, $T stands for the directory in which this file
If lyskomd should dump a core for some reason the core file will be
written in the directory `cores'.
8) Fix updateLysKOM
10) Fix updateLysKOM
Edit the script updateLysKOM and fix the path to lyskomd. When
finished, do
......@@ -186,7 +195,7 @@ In the following, $T stands for the directory in which this file
program in the next release of LysKOM.
9) Arrange so that cron will run updateLysKOM regurlarly.
11) Arrange so that cron will run updateLysKOM regurlarly.
If you are running on a sun you can do like this:
......@@ -198,7 +207,7 @@ In the following, $T stands for the directory in which this file
to /etc/crontab.
10) Fetch the most recent lyskom client from ftp.lysator.liu.se. Since
12) Fetch the most recent lyskom client from ftp.lysator.liu.se. Since
currently the only working client is written in emacs lisp, you will
have to get the elisp program elisp-client and install it so that
your load-path in emacs finds it. Wait until cron starts lyskomd,
......@@ -224,12 +233,12 @@ In the following, $T stands for the directory in which this file
Announce the new LysKOM server to the intended audience.
11) We would like to know about where LysKOM servers are running. If
13) We would like to know about where LysKOM servers are running. If
you start a server, please mail "kom@lysator.liu.se". We will tell
you when we make new releases, and warn you if we should find any
serious problems.
12) Read the file doc/ADMINISTRATION.
14) Read the file doc/ADMINISTRATION.
LysKOM needs your attention once in a while. Here at Lysator we
expunge old texts (with "dbck -g") approximately once every 2
......
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