--configtest: remember if MOTD is configured by file or phrase

[ngircd-alex.git] / INSTALL

diff --git a/INSTALL b/INSTALL
index 227c46264c0a065daba5027186bc67b4d329eee5..f7e51a164c36a8becb2d69d4dab2d853b897a26b 100644 (file)
--- a/INSTALL
+++ b/INSTALL
@@ -1,7 +1,7 @@
 
                      ngIRCd - Next Generation IRC Server
 
 
                      ngIRCd - Next Generation IRC Server
 

-                        (c)2001-2007 Alexander Barton,
+                        (c)2001-2010 Alexander Barton,

                     alex@barton.de, http://www.barton.de/
 
                ngIRCd is free software and published under the
                     alex@barton.de, http://www.barton.de/
 
                ngIRCd is free software and published under the


@@ -9,11 +9,15 @@
 
                                 -- INSTALL --
 
 
                                 -- INSTALL --
 

-                         

 
 I. Upgrade Information
 ~~~~~~~~~~~~~~~~~~~~~~
 
 
 I. Upgrade Information
 ~~~~~~~~~~~~~~~~~~~~~~
 

+Differences to version 16
+
+- Changes to the "MotdFile" specified in ngircd.conf now require a ngircd
+  configuration reload to take effect (HUP signal, REHASH command).
+

 Differences to version 0.9.x
 
 - The option of the configure script to enable support for Zeroconf/Bonjour/
 Differences to version 0.9.x
 
 - The option of the configure script to enable support for Zeroconf/Bonjour/


@@ -51,9 +55,9 @@ on modern UNIX-like systems that are supported by GNU autoconf and GNU
 automake ("configure") should be no problem.
 
 The normal installation procedure after getting (and expanding) the source
 automake ("configure") should be no problem.
 
 The normal installation procedure after getting (and expanding) the source

-files (using a distribution archive or CVS) is as following:
+files (using a distribution archive or GIT) is as following:

 
 

-  1) ./autogen.sh      [only necessary when using CVS]
+  1) ./autogen.sh      [only necessary when using GIT]

   2) ./configure
   3) make
   4) make install
   2) ./configure
   3) make
   4) make install


@@ -77,7 +81,7 @@ doc/ directory: sample-ngircd.conf.
 
 The first step, autogen.sh, is only necessary if the configure-script isn't
 already generated. This never happens in official ("stable") releases in
 
 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.
+tar.gz-archives, but when using GIT.

 
 This step is therefore only interesting for developers.
 
 
 This step is therefore only interesting for developers.
 


@@ -184,6 +188,24 @@ standard locations.
   to the daemon, for example by using "/etc/hosts.{allow|deny}".
   The "libwrap" is required for this option.
 
   to the daemon, for example by using "/etc/hosts.{allow|deny}".
   The "libwrap" is required for this option.
 

+* PAM:
+  --with-pam[=<path>]
+
+  Enable support for PAM, the Pluggable Authentication Modules library.
+  See doc/PAM.txt for details.
+
+* SSL:
+  --with-openssl[=<path>]
+  --with-gnutls[=<path>]
+
+  Enable support for SSL/TLS using OpenSSL or gnutls libraries.
+  See doc/SSL.txt for details.
+
+* IPv6:
+  --enable-ipv6
+
+  Adds support for version 6 of the Internet Protocol.
+

 
 IV. Useful make-targets
 ~~~~~~~~~~~~~~~~~~~~~~~
 
 IV. Useful make-targets
 ~~~~~~~~~~~~~~~~~~~~~~~


@@ -244,7 +266,3 @@ These parameters could be passed to the ngIRCd:
 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.
 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.26 2007/04/08 11:39:08 alex Exp $