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

All documentation removed. Refer to

parent 6df6cf44
.\" $Id: lyskomd.8,v 1.31 1998/12/26 22:40:16 byers Exp $
.\" $Id: lyskomd.8,v 1.32 1999/04/03 15:10:28 ceder Exp $
.\" Copyright (C) 1991, 1994 Lysator Academic Computer Association.
.\" This file is part of the LysKOM server.
......@@ -21,9 +21,9 @@
.\" Please mail bug reports to
.\" $Id: lyskomd.8,v 1.31 1998/12/26 22:40:16 byers Exp $
.\" $Date: 1998/12/26 22:40:16 $
.TH lyskomd 8 "January 12, 1994" "Lysator"
.\" $Id: lyskomd.8,v 1.32 1999/04/03 15:10:28 ceder Exp $
.\" $Date: 1999/04/03 15:10:28 $
.TH lyskomd 8 "April 3, 1999" "Lysator"
lyskomd - LysKOM server
......@@ -34,482 +34,8 @@ lyskomd - LysKOM server
.B config-file
This documents lyskomd release 1.9.0. lyskomd is a LysKOM server.
The server reads a configuration file (see CONFIGURATION below) and
then listens for connections on the given ports (defaults are 4894
for the
.I client_port
and 4895 for the
.IR mux_port ).
.B \-d
Adds one to the debug-level i.e. increases the amount of output on the
stderr from the process. This option can be given repeatedly. If it
is given, lyskomd will not run as a daemon, but rather stay in
foreground mode.
Using one
.B \-d
make the process print a
.I >
for every timeout, a message for every person that is connecting or
disconnecting and a message for every successful or unsuccessful
communication to the process.
The configuration file is line oriented.
Each line consists of one
.B parameter name,
a colon, and the
.B parameter value.
Empty lines, and lines whose first non-blank character is #, are
comment lines and ignored.
The configuration file is normally found in
.B /usr/lyskom/etc/config,
but the exact location can be changed at compile time (for instance
by specifying
.BI --prefix= pathname
when running
.BR configure )
or at run time (by specifying a config file as an argument).
Some parameters take a
.B bool
as the parameter value. Legal values for a
.B bool
.B false, off, no
.B 0
to turn the feature off, or
.B true, on, yes
.B 1
to turn it on.
The following parameters can be set in the config file:
.B Locale: locale_name
.I locale_name
as the locale to run in.
This parameter is only available on systems which support the
.B setlocale()
call. If this parameter is not set, no call to
.B setlocale()
will be made.
.B Force ISO 8859-1: bool
This option is provided for those with ancient computers that cannot
.B setlocale()
properly. If this is set, lyskomd will handle texts according to the
ISO 8859-1 (latin1) alphabet. Default value:
.I no
.B Prefix: prefix
The default value of
.I prefix
.B /usr/lyskom
(unless changed in server-config.c).
All files that the server uses are found in sub-directories of this
directory. See FILES below.
.B Send async: bool
Do not send any non-requested messages. This disables the sending of
messages about events in the server to all connections.
Use of this parameter is not recommended. This option is on by
.B Client port: portname
Listen for new clients on
.I portname,
which can be a symbolic port name (traditionally looked up in
.B /etc/services)
or a port number. This defaults to 4894, and all clients currently
expect that number.
.B Mux port: portname
Listen for mux connections on
.I portname.
Muxes can be used to multiplex several clients on a single file
descriptor. The mux runs as a separate process. This was used
historically when LysKOM ran on a machine were only 20 file
descriptors coule be open at once. The mux code has not been
released. Send a mail to
if you need it. The default port number is 4895.
.B Presentation of conferences: conf-no
The number of the conference where presentations should be sent.
Defaults to 1. This option is ignored in lyskomd 1.9 and later. Use
dbck or protocol A to set it instead.
.B Presentation of persons: conf-no
The number of the conference where presentations should be sent.
Defaults to 2. This option is ignored in lyskomd 1.9 and later. Use
dbck or protocol A to set it instead.
.B Motd-conference: conf-no
The number of the conference where "message-of-the-day" messages
should be sent.
Defaults to 3. This option is ignored in lyskomd 1.9 and later. Use
dbck or protocol A to set it instead.
.B News-conference: conf-no
The number of the conference where news of interest to the readers of
this LysKOM server should be written. This is typically a conference
with very low traffic which everyone shoule be a member of. Clients
should offer new users to join it.
Defaults to 4. This option is ignored in lyskomd 1.9 and later. Use
dbck or protocol A to set it instead.
.B Message of the day: text-no
Default message-of-the-day of this server.
The text will be showed automatically by conforming LysKOM clients
when a user logs on. This option is ignored in lyskomd 1.9 and later. Use
dbck or protocol A to set it instead.
.B Garb: bool
Should the database be automatically purged of old texts? Default
.I on
.B Never save: bool
Do not use unless you know what you are doing.
(Note: there is currently no-one in the LysKOM development group which
knows exactly what this option does!)
.B Log accesses: filename
This parameter can only be set if the server has been compiled with
defined. It will save a trace of all activity in the database to a
file, for later use in simulations et c.
Compiling with
slows the server down quite a lot, so it is normally not defined.
.B Data file: data_file
Part of the data base will be held in
.I prefix/data_file.
.B Backup file: backup_file
The file
.I prefix/backup_file
will always contain a complete data base, but it might be a little
.B Backup file 2: backup_file_2
The file
.I prefix/backup_file_2
will contains the previous generation of backup_file. It may be
needed in case an error inte the backup_file is detected during the
creation of data_file.
.B Text file: text_file
The file
.I prefix/text_file
holds all actual text which is written.
.B Text backup file: backup_text
When dbck is run with the
.I -g
option (see dbck(8)) it will store the previous contents of
.I prefix/text_file
.I prefix/backup_text.
This file is never used by lyskomd itself.
.B Log file: log_file
Log messages from lyskomd will be written to
.I prefix/log_file.
.B Log statistics: stat_file
Whenever lyskomd receives a SIGHUP it will append a timestamp and
a count of how many different atomic calls have been made in
.I prefix/stat_file.
.B Pid file: pid_file
When lyskomd is up-and-running it will write its pid in the file
.I prefix/pid_file.
This file is not currently used as a log file. It is present here
only so that the updateLysKOM script can easily find out what pid the
LysKOM server has.
.B Memory usage file: mem_file
When lyskomd exits normally it appends some info on its usage of
memory to
.I prefix/mem_file.
Almost any memory leak bugs should be detectable by looking in this
.B Aux-item definition file: aux_def_file
This files defines which aux-infos the server should support, and how
it should handle them. See the Texinfo documentation.
.B Idle timeout: idle
Number of milliseconds to sleep when there is nothing for lyskomd
to do.
.B Garb timeout: garb
Number of milliseconds to sleep when the server is garbaging texts,
but has nothing else important to do.
.B Permissive sync: bool
Turning this option on lets any session sync the LysKOM database.
Turning it off restricts the operation to LysKOM administrators.
.B Sync timeout: sync
Number of milliseconds to sleep when lyskomd is saving its database.
Defaults to 0.
.B Garb interval: garb_interval
Number of minutes between each garb sweep. Defaults to 1440, that is,
a garb sweep will be run once per day.
.B Sync interval: sync_interval
Number of minutes between syncs. Currently, lyskomd holds part of the
data base in main memory. It is dumped to
.I prefix/data_file
periodically. This parameter determines the period.
.B Sync retry interval: retry_interval
If anything goes wrong while trying to dump the data base to
.I prefix/data_file
(such as if the disk is full),
lyskomd will wait for this many minutes before trying again.
.B Max conference name length: int
.B Max password length: int
Only the first eight characters of the password are currently
significant, even if this number is much larger.
.B Max what am I doing length: int
.B Max username length: int
.B Max text length: int
.B Max broadcast length: int
.B Max regexp length: int
.B Max marks per person: int
.B Max marks per text: int
.B Max recipients per text: int
.B Max comments per text: int
.B Max footnotes per text: int
.B Max links per text: int
.B Max mark_as_read chunks: int
.B Max super_conf loop: int
.B Max accept_async len: int
Maximum length of list accepted in the accept_async call.
.B Max aux_items deleted per call: int
Maximum number of aux_items that can be deleted in one call.
.B Max aux_items added per call: int
Maximum number of aux_items that can be added at once.
.B Default garb nice: int
Each conference has a lifetime for texts written in it.
The lifetime is counted in days, and can be set for each conference by
the administrator of the conference.
This is the default value assigned to new conferences.
.B Max client transmit queue: int
Mux number of pending data blocks in the reply queue to a client. If
there is ever more than this many data blocks in the queue the client
will be disconnected. Each atomic question typically generates two
data blocks.
.B Max simultaneous client replies: int
This is a performance tuning parameter of little real interest.
.B Open files: int
Try to persuade the operating system to allow lyskomd to have this
many open file descriptors simultaneously. Each client that is
connected to the server occupies one file descriptor, and
.I lyskomd
needs several file descriptors for internal purposes.
.B Anyone can create new persons: bool
If this is set, anyone can create a new person, even if he lacks
special bits for doing so.
.B Anyone can create new conferences: bool
If this is set, anyone can create a new conferences, even if he lacks
special bits for doing so.
.B Allow creation of persons before login: bool
If this is set, persons can connect the the server and create a new
person without logging in. This is how new users register in open
.B Default change name capability: bool
If this is set, new users are created with the ability to change their
own name.
.B Ident-authentication: policy
Decide how strictly the server should use the IDENT protocol.
.B policy
can take any of three values:
.I off
.I never:
Do not use the IDENT protocol.
.I on
.I try:
Use it, but allow logins even if the lookup fails.
.I require
.I required:
Disallow connections if the server cannot find a IDENT login name.
.B Log login: bool
Should logins be logged to the log file? Default value:
.I off.
.B Cache conference limit: int
How many conference statuses the server cache should hold in main
.B Cache person limit: assign_int
How many person statuses the server cache should hold in main
.B Cache text_stat limit: assign_int
How many text statuses the server cache should hold in main
.B Echo: text_string
.I text_string
in the log.
.B Jubel: pers_no text_no
State that
.I pers_no
is not allowed to create text number
.I text_no
.B Jubel: pers_no divident remainder
Say that
.I pers_no
is not allowed to create any text number
.I T
which meets the condition
.I T \% divident == remainder
.B Add members by invitation: bool
If this is set, then adding others as members to a conference sets the
invitation bit of the membership. If this is off, the membership bit is
set to whatever the caller specifies. The default is to set this.
.B Allow secret memberships: bool
If this is set, then memberships may be secret. Otherwise any attempt
to create a secret membership or change an existing membership to a
secret membership will fail. This is set by default.
.B allow reinvitations: bool
If this is set, then it is possible to set the invitation bit of a
membership even after it has been cleared. If it is not set, then the
invitation bit of a conference type can only be set when the
membership is created. It can be cleared at any time. This is off by
.B regexps use collate table: bool
If this is set, regexp matching of conference names uses the same
collate table used by regular matching. This usually implies that the
regexp "foo" will match "foo", "Foo", "fOo" and several other
variants. The defalt is on.
There are some signals that have a special meaning to the LysKOM
Logs out all sessions, saves the database and exits normally.
Saves the database and dump core. (This should only be used for
debugging purposes.)
Print statistics about how often different commands have been used
since the process started.
Forks a child that immediately dumps core. The main process just waits
until the child is done and then continues. (This does not work on
.TP 20
.B /usr/lyskom
Default value of
.I prefix.
.IB prefix /db/lyskomd-data
Half of the database: all status information.
.IB prefix /db/lyskomd-texts
The other half of the database: the actual texts.
.IB prefix /db/lyskomd-backup
A backup copy of
.I lyskomd-data.
Never, ever delete this file unless you know what you are doing, or
you may lose the entire data base. Most of the time this is the only
complete database file!
.IB prefix /etc/pid
File with the pid of the lyskom-process.
.IB prefix /etc/memory-usage
On normal exit,
.I lyskomd
will append some statistics to this file. It can be used for
detecting memory leaks.
.IB prefix /etc/aux-items.conf
This file contains definitions of the aux-items that the server should
support. It is read by
.I lyskomd
at startup. See the Texinfo documentation for more information.
lyskomd should re-read the config file when a SIGHUP is received.
lyskomd should terminate when a SIGINT or SIGTERM is received.
A very small memory leak still remains.
There is no practical handling of security.
The choice of asynchronously issued messages is not very good.
It uses too much memory.
In 1990, Per Cederqvist <> and Peter Eriksson
<> and a few other persons started to write the
server. It was operational in the summer of 1990, even though the
members of Lysator discovered a thing called MUD. We started using
RCS on 20 May 1991. The first release was made on 16 Sept 1991.
Around that time we switched from RCS to CVS, and ceder started to
write pcl-cvs (a GNU Emacs front-end to CVS) instead of LysKOM. After
a while, he started writing Bugtrack, to be able to handle all bug
reports he recieved about pcl-cvs. He hopes to be able to devote some
more time to LysKOM in the future.
Contact Per Cederqvist if you want commercial support of LysKOM.
lyskomd is a LysKOM server.
Full documentation can be found in the Texinfo manual "lyskomd 2.0.0
Reference Manual" (found in info format as
.BR ).
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