commit 98b92e112a38981dcb9e3fef87ca87dd94466e63
from: Alexander Barton <alex@barton.de>
date: Fri Sep 03 20:02:02 2004 UTC

Information for configuring ngIRCd. From HEAD.

commit - 2d524b195878481985615e0d674e98112a94d112
commit + 98b92e112a38981dcb9e3fef87ca87dd94466e63
blob - dc6d102b317a61157ea7fe0bf73ec4fa7abaaa51
blob + e9ac456c1bd2cfacff93ce8f343e7a32a5f5e53f
--- INSTALL
+++ INSTALL
@@ -46,7 +46,21 @@ files (using a distribution archive or CVS) is as foll
   3) make
   4) make install
 
+(Please see details below!)
 
+Now the newly compiled executable "ngircd" is installed in its standard
+location, /usr/local/sbin/.
+
+The next step is to configure and afterwards starting the daemon. Please
+have a look at the ngircd(8) and ngircd.conf(5) manual pages for details
+and all possible options.
+
+If no previous version of the configuration file exists (the standard name
+is /usr/local/etc/ngircd.conf), a sample configuration file containing all
+possible options will be installed there. You'll find its template in the
+doc/ directory: sample-ngircd.conf.
+
+
 1): "autogen.sh"
 
 The first step, autogen.sh, is only necessary if the configure-script isn't
@@ -163,4 +177,4 @@ number. In both cases the server exits after the outpu
 
 
 -- 
-$Id: INSTALL,v 1.18.2.1 2004/05/07 11:24:17 alex Exp $
+$Id: INSTALL,v 1.18.2.2 2004/09/03 20:02:02 alex Exp $