commit 0b1635e371e9c46beb01ebf684526c2ccda8ecea from: Alexander Barton date: Mon May 20 12:02:58 2002 UTC - Dokumentation aktualisiert. commit - 74f971284e22505df5cafad491f9846fe84ff729 commit + 0b1635e371e9c46beb01ebf684526c2ccda8ecea blob - 60fde8a017fc36f5c869dc6f7cbd6e312f93b319 blob + 37704075c4b1803830d68b270310964572805c87 --- INSTALL +++ INSTALL @@ -81,8 +81,8 @@ Folgende Dateien werden installiert: - /usr/local/etc/ngircd.conf: Beispiel-Konfiguration, wenn nicht vorhanden -III. Nuetzliche make-Targets -~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +II. Nuetzliche make-Targets +~~~~~~~~~~~~~~~~~~~~~~~~~~~ Die vom configure-Script erzeugten Makefile's enthalten immer die folgenden nuetzlichen Targets: @@ -98,8 +98,8 @@ nuetzlichen Targets: -IV. Konfigurationsdatei ngircd.conf -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +III. Konfigurationsdatei ngircd.conf +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In der Konfigurationsdatei werden Kommentare durch "#" oder durch ";" eingeleitet. Dieses dient nur der besseren Lesbarkeit. @@ -117,8 +117,8 @@ Die Bedeutung der einzelnen Variablen ist in der Beisp Konfigurationsdatei vorhanden ist. -V. Kommandozeilen-Optionen -~~~~~~~~~~~~~~~~~~~~~~~~~~ +IV. Kommandozeilen-Optionen +~~~~~~~~~~~~~~~~~~~~~~~~~~~ Folgende Parameter koennen dem ngIRCd u.a. uebergeben werden: @@ -145,4 +145,4 @@ Server nach der Ausgabe wieder. -- -$Id: INSTALL,v 1.6 2002/05/08 15:44:43 alex Exp $ +$Id: INSTALL,v 1.7 2002/05/20 12:02:58 alex Exp $ blob - 13517e5f63452330e8ae837f01369b488e806e7b blob + 59ae7656f31599eac976755deaad649f0590b424 --- doc/en/INSTALL +++ doc/en/INSTALL @@ -10,8 +10,117 @@ -- INSTALL -- -Sorry, the english INSTALL text is not yet available ... +I. Standard-Installation +~~~~~~~~~~~~~~~~~~~~~~~~ +ngIRCd is developed for UNIX-like systems, which means, that the installation +on a modern UNIX-like system should be no problem. The only thing is, that +the system should be supported by GNU automake and GNU autoconf ("configure"). + +The normal installation is like that: + + 1) tar xzf ngircd-.tar.gz + 2) cd ngircd- + 3) ./autogen.sh [only necessary when using CVS] + 4) ./configure + 5) make + 6) make install + +3): "autogen.sh" + +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-archieves, but when using the CVS system. + +The next is therefore only interesting for developpers. + +autogen.sh produces the makefile.in's, which are necessary for the configure +script it self, and some more files for make. For this step, there must be +GNU automake and GNU autoconf (in recent versions). + +(again: "end users" do not need this step!) + +to 4): "./configure" + +The configure-script is used to detect local system dependancies. + +In the perfect case, configure should recognize all needed libraries, header +and so on. If this shouldn't work, "./configure --help" shows more options. + +to 5): "make" + +The make command uses the Makefiles produced by configure and compiles the +ngIRCd daemon. + +to 6): "make install" + +Use "make install" to install the server and a sample configuration file on +the local system. For this step, root privileges are necessary. If there is +already an older configuration file present, it won't be overwritten. + +This are the files that are installed: + +- /usr/local/sbin/ngircd: exectable server +- /usr/local/etc/ngircd.conf: sample configuration, if not there + + +II. Useful make-targets +~~~~~~~~~~~~~~~~~~~~~~~ + +The Makefile produced by the configure-script contain always these useful +targets: + + - clean: delete every product from the compiler/linker + next step: -> make + + - distclean: plus erase all generated Makefiles + next step: -> ./configure + + - maintainer-clean: erease all automatic generated files + next step: -> ./autogen.sh + + +III. Sample configuration file ngircd.conf +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +In the sample configuration file, there are comments beginning with "#" OR +";" -- this is only for the better understanding of the code. + +The file is seperated in three blocks: [Global], [Operator], [Server]. In +the [Gobal] part, there is the main configuration, like the server-name +and the ports, on which the server should be listening. In the [Operator] +section, the server-operators are defined and [Server] is the section, +where the server-links are configured. + +The meaning of the variables in the configuration file is explained in the +"doc/sample-ngircd.conf", which is also the sample configuration file in +/usr/local/etc after running "make install" (if you don't already have one). + + +IV. Command line options +~~~~~~~~~~~~~~~~~~~~~~~~ + +These parameters could be passed to the ngIRCd: + +-f, --config + The daemon uses the file as configuration file rather than + the standard configuration /usr/local/etc/ngircd.conf. + +-n, --nodaemon + ngIRCd should be running as a foreground process. + +-p, --passive + Server-links won't be automatically established. + +--configtest + Reads, validates and dumps the configuration file as interpreted + by the server. Then exits. + +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. + + -- -$Id: INSTALL,v 1.1 2002/05/08 15:43:00 alex Exp $ +$Id: INSTALL,v 1.2 2002/05/20 12:02:58 alex Exp $ blob - 67325a02e77e9a5c707f80cd28f73297c91bc3ce blob + 84d256a9dfcb06ff8fe893f6ab3bb58cc27405cc --- doc/en/README +++ doc/en/README @@ -28,7 +28,7 @@ II. Status At present, the ngIRCd is under active development, some features are not implemented, some only partly. -Till tody (more or less complete) implemented IRC-commands: +Till today (more or less complete) implemented IRC-commands: AWAY, DIE, ERROR, ISON, JOIN, KILL, LINKS, LIST, LUSERS, MODE, MOTD, NAMES, NICK, NOTICE, NJOIN, OPER, PART, PASS, PING, PONG, PRIVMSG, QUIT, RESTART, @@ -97,4 +97,4 @@ to post a mail to: or