INSTALL 6.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186
  1. ngIRCd - Next Generation IRC Server
  2. (c)2001-2004 by Alexander Barton,
  3. alex@barton.de, http://www.barton.de/
  4. ngIRCd is free software and published under the
  5. terms of the GNU General Public License.
  6. -- INSTALL --
  7. I. Upgrade Information
  8. ~~~~~~~~~~~~~~~~~~~~~~
  9. Differences to version 0.8.x
  10. - The maximum length of passwords has been raised to 20 characters (instead
  11. of 8 characters). If your passwords are longer than 8 characters then they
  12. are cut at an other position now.
  13. Differences to version 0.6.x
  14. - Some options of the configure script have been renamed:
  15. --disable-syslog -> --without-syslog
  16. --disable-zlib -> --without-zlib
  17. Please call "./configure --help" to review the full list of options!
  18. Differences to version 0.5.x
  19. - Starting with version 0.6.0, other servers are identified using asynchronous
  20. passwords: therefore the variable "Password" in [Server]-sections has been
  21. replaced by "MyPassword" and "PeerPassword".
  22. - New configuration variables, section [Global]: MaxConnections, MaxJoins
  23. (see example configuration file "doc/sample-ngircd.conf"!).
  24. II. Standard Installation
  25. ~~~~~~~~~~~~~~~~~~~~~~~~~
  26. ngIRCd is developed for UNIX-based systems, which means that the installation
  27. on modern UNIX-like systems that are supported by GNU autoconf and GNU
  28. automake ("configure") should be no problem.
  29. The normal installation procedure after getting (and expanding) the source
  30. files (using a distribution archive or CVS) is as following:
  31. 1) ./autogen.sh [only necessary when using CVS]
  32. 2) ./configure
  33. 3) make
  34. 4) make install
  35. (Please see details below!)
  36. Now the newly compiled executable "ngircd" is installed in its standard
  37. location, /usr/local/sbin/.
  38. The next step is to configure and afterwards starting the daemon. Please
  39. have a look at the ngircd(8) and ngircd.conf(5) manual pages for details
  40. and all possible options.
  41. If no previous version of the configuration file exists (the standard name
  42. is /usr/local/etc/ngircd.conf), a sample configuration file containing all
  43. possible options will be installed there. You'll find its template in the
  44. doc/ directory: sample-ngircd.conf.
  45. 1): "autogen.sh"
  46. The first step, autogen.sh, is only necessary if the configure-script isn't
  47. already generated. This never happens in official ("stable") releases in
  48. tar.gz-archives, but when using CVS.
  49. This step is therefore only interesting for developers.
  50. autogen.sh produces the Makefile.in's, which are necessary for the configure
  51. script itself, and some more files for make. To run autogen.sh you'll need
  52. GNU autoconf and GNU automake (use recent versions! autoconf 2.53 and
  53. automake 1.6.1 are known to work).
  54. Again: "end users" do not need this step!
  55. 2): "./configure"
  56. The configure-script is used to detect local system dependencies.
  57. In the perfect case, configure should recognise all needed libraries, header
  58. files and so on. If this shouldn't work, "./configure --help" shows all
  59. possible options.
  60. In addition, you can pass some command line options to "configure" to enable
  61. and/or disable some features of ngIRCd. All these options are shown using
  62. "./configure --help", too.
  63. Compiling a static binary will avoid you the hassle of feeding a chroot dir
  64. (if you want use the chroot feature). Just do something like:
  65. CFLAGS=-static ./configure [--your-options ...]
  66. Then you can use a void directory as ChrootDir (like OpenSSH's /var/empty).
  67. 3): "make"
  68. The make command uses the Makefiles produced by configure and compiles the
  69. ngIRCd daemon.
  70. 4): "make install"
  71. Use "make install" to install the server and a sample configuration file on
  72. the local system. Normally, root privileges are necessary to complete this
  73. step. If there is already an older configuration file present, it won't be
  74. overwritten.
  75. This files will be installed by default:
  76. - /usr/local/sbin/ngircd: executable server
  77. - /usr/local/etc/ngircd.conf: sample configuration (if not already present)
  78. - /usr/local/share/doc/ngircd/: documentation
  79. II. Useful make-targets
  80. ~~~~~~~~~~~~~~~~~~~~~~~
  81. The Makefile produced by the configure-script contains always these useful
  82. targets:
  83. - clean: delete every product from the compiler/linker
  84. next step: -> make
  85. - distclean: the above plus erase all generated Makefiles
  86. next step: -> ./configure
  87. - maintainer-clean: erase all automatic generated files
  88. next step: -> ./autogen.sh
  89. III. Sample configuration file ngircd.conf
  90. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  91. In the sample configuration file, there are comments beginning with "#" OR
  92. ";" -- this is only for the better understanding of the file.
  93. The file is separated in four blocks: [Global], [Operator], [Server], and
  94. [Channel].
  95. In the [Global] section, there is the main configuration like the server
  96. name and the ports, on which the server should be listening. IRC operators
  97. of this server are defined in [Operator] blocks. [Server] is the section
  98. where server links are configured. And [Channel] blocks are used to
  99. configure pre-defined ("persistent") IRC channels.
  100. The meaning of the variables in the configuration file is explained in the
  101. "doc/sample-ngircd.conf", which is used as sample configuration file in
  102. /usr/local/etc after running "make install" (if you don't already have one)
  103. and in the "ngircd.conf" manual page.
  104. IV. Command line options
  105. ~~~~~~~~~~~~~~~~~~~~~~~~
  106. These parameters could be passed to the ngIRCd:
  107. -f, --config <file>
  108. The daemon uses the file <file> as configuration file rather than
  109. the standard configuration /usr/local/etc/ngircd.conf.
  110. -n, --nodaemon
  111. ngIRCd should be running as a foreground process.
  112. -p, --passive
  113. Server-links won't be automatically established.
  114. -t, --configtest
  115. Reads, validates and dumps the configuration file as interpreted
  116. by the server. Then exits.
  117. Use "--help" to see a short help text describing all available parameters
  118. the server understands, with "--version" the ngIRCd shows its version
  119. number. In both cases the server exits after the output.
  120. --
  121. $Id: INSTALL,v 1.21 2005/02/10 08:20:09 alex Exp $