ngircd-tor/INSTALL

162 lines
5.0 KiB
Plaintext
Raw Normal View History

ngIRCd - Next Generation IRC Server
2003-03-04 14:46:53 +01:00
(c)2001-2003 by Alexander Barton,
alex@barton.de, http://www.barton.de/
2003-03-04 14:46:53 +01:00
ngIRCd is free software and published under the
terms of the GNU General Public License.
2003-03-04 14:46:53 +01:00
-- INSTALL --
2002-12-18 13:19:07 +01:00
2003-03-04 14:46:53 +01:00
2002-12-18 13:19:07 +01:00
2003-03-04 14:46:53 +01:00
I. Upgrade Information
~~~~~~~~~~~~~~~~~~~~~~
2002-12-18 13:19:07 +01:00
2003-03-07 15:45:10 +01:00
Differences to version 0.6.x
- Some options of the configure script have been renamed:
--disable-syslog -> --without-syslog
--disable-zlib -> --without-zlib
Please call "./configure --help" to review the full list of options!
2003-03-04 14:46:53 +01:00
Differences to version 0.5.x
2002-12-18 13:19:07 +01:00
- Starting with version 0.6.0, other servers are identified using asynchronous
2003-03-04 14:46:53 +01:00
passwords: therefore the variable "Password" in [Server]-sections has been
replaced by "MyPassword" and "PeerPassword".
2003-03-04 14:46:53 +01:00
- New configuration variables, section [Global]: MaxConnections, MaxJoins
(see example configuration file "doc/sample-ngircd.conf"!).
2003-03-04 14:46:53 +01:00
II. Standard Installation
~~~~~~~~~~~~~~~~~~~~~~~~~
2003-03-24 00:13:15 +01:00
ngIRCd is developed for UNIX-based systems, which means that the installation
on modern UNIX-like systems that are supported by GNU autoconf and GNU
2003-03-04 14:46:53 +01:00
automake ("configure") should be no problem.
2003-03-04 14:46:53 +01:00
The normal installation procedure after getting (and expanding) the source
files (using a distribution archive or CVS) is as following:
2003-03-04 14:46:53 +01:00
1) ./autogen.sh [only necessary when using CVS]
2) ./configure
3) make
4) make install
2003-03-08 13:34:55 +01:00
2003-03-04 14:46:53 +01:00
1): "autogen.sh"
2003-03-04 14:46:53 +01:00
The first step, autogen.sh, is only necessary if the configure-script isn't
already generated. This never happens in official ("stable") releases in
tar.gz-archives, but when using CVS.
This step is therefore only interesting for developers.
2003-03-04 14:46:53 +01:00
autogen.sh produces the Makefile.in's, which are necessary for the configure
script itself, and some more files for make. To run autogen.sh you'll need
2003-03-08 13:34:55 +01:00
GNU autoconf and GNU automake (use recent versions! autoconf 2.53 and
automake 1.6.1 are known to work).
2003-03-04 14:46:53 +01:00
Again: "end users" do not need this step!
2003-03-08 13:34:55 +01:00
2): "./configure"
The configure-script is used to detect local system dependencies.
In the perfect case, configure should recognise all needed libraries, header
2003-03-04 14:46:53 +01:00
files and so on. If this shouldn't work, "./configure --help" shows all
possible options.
2003-03-04 14:46:53 +01:00
In addition, you can pass some command line options to "configure" to enable
and/or disable some features of ngIRCd. All these options are shown using
"./configure --help", too.
2003-03-08 13:34:55 +01:00
3): "make"
2002-05-08 17:44:43 +02:00
2003-03-04 14:46:53 +01:00
The make command uses the Makefiles produced by configure and compiles the
ngIRCd daemon.
2002-05-08 17:44:43 +02:00
2003-03-08 13:34:55 +01:00
4): "make install"
2002-05-08 17:44:43 +02:00
2003-03-04 14:46:53 +01:00
Use "make install" to install the server and a sample configuration file on
the local system. Normally, root privileges are necessary to complete this
step. If there is already an older configuration file present, it won't be
overwritten.
2002-05-08 17:44:43 +02:00
2003-03-04 14:46:53 +01:00
This files will be installed by default:
2002-05-08 17:44:43 +02:00
- /usr/local/sbin/ngircd: executable server
2003-03-04 14:46:53 +01:00
- /usr/local/etc/ngircd.conf: sample configuration (if not already present)
2003-04-22 01:31:39 +02:00
- /usr/local/share/doc/ngircd/: documentation
2003-03-04 14:46:53 +01:00
II. Useful make-targets
~~~~~~~~~~~~~~~~~~~~~~~
2003-03-04 14:46:53 +01:00
The Makefile produced by the configure-script contains always these useful
targets:
2003-03-04 14:46:53 +01:00
- clean: delete every product from the compiler/linker
next step: -> make
2003-03-04 14:46:53 +01:00
- distclean: the above plus erase all generated Makefiles
next step: -> ./configure
- maintainer-clean: erase all automatic generated files
2003-03-04 14:46:53 +01:00
next step: -> ./autogen.sh
2002-03-03 14:07:01 +01:00
2003-03-04 14:46:53 +01:00
III. Sample configuration file ngircd.conf
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2002-05-08 17:44:43 +02:00
2003-03-04 14:46:53 +01:00
In the sample configuration file, there are comments beginning with "#" OR
";" -- this is only for the better understanding of the file.
2002-05-08 17:44:43 +02:00
The file is separated in four blocks: [Global], [Operator], [Server], and
2003-03-10 01:23:34 +01:00
[Channel].
In the [Global] section, there is the main configuration like the server
name and the ports, on which the server should be listening. IRC operators
of this server are defined in [Operator] blocks. [Server] is the section
where server links are configured. And [Channel] blocks are used to
2003-03-04 14:46:53 +01:00
configure pre-defined ("persistent") IRC channels.
2002-05-08 17:44:43 +02:00
2003-03-04 14:46:53 +01:00
The meaning of the variables in the configuration file is explained in the
"doc/sample-ngircd.conf", which is used as sample configuration file in
2003-03-10 01:23:34 +01:00
/usr/local/etc after running "make install" (if you don't already have one)
and in the "ngircd.conf" manual page.
2002-05-08 17:44:43 +02:00
2003-03-04 14:46:53 +01:00
IV. Command line options
~~~~~~~~~~~~~~~~~~~~~~~~
2002-05-08 17:44:43 +02:00
2003-03-04 14:46:53 +01:00
These parameters could be passed to the ngIRCd:
2002-05-08 17:44:43 +02:00
-f, --config <file>
2003-03-04 14:46:53 +01:00
The daemon uses the file <file> as configuration file rather than
the standard configuration /usr/local/etc/ngircd.conf.
2002-05-08 17:44:43 +02:00
-n, --nodaemon
2003-03-04 14:46:53 +01:00
ngIRCd should be running as a foreground process.
2002-05-08 17:44:43 +02:00
-p, --passive
2003-03-04 14:46:53 +01:00
Server-links won't be automatically established.
2002-05-08 17:44:43 +02:00
--configtest
2003-03-04 14:46:53 +01:00
Reads, validates and dumps the configuration file as interpreted
by the server. Then exits.
2002-05-08 17:44:43 +02:00
2003-03-04 14:46:53 +01:00
Use "--help" to see a short help text describing all available parameters
the server understands, with "--version" the ngIRCd shows its version
number. In both cases the server exits after the output.
2002-05-08 17:44:43 +02:00
2002-03-03 14:07:01 +01:00
--
2003-04-22 01:31:39 +02:00
$Id: INSTALL,v 1.16 2003/04/21 23:31:39 alex Exp $