Fix spelling in some documents.

[ngircd-alex.git] / doc / FAQ.txt

diff --git a/doc/FAQ.txt b/doc/FAQ.txt
index a44fb71785590282b9129b96623260cbb0fe07b6..bf3628c12bea03d8196029316babd0d0882f7880 100644 (file)
--- a/doc/FAQ.txt
+++ b/doc/FAQ.txt
@@ -17,7 +17,7 @@ A: Yes. ngIRCd is compatible to the original ircd used by IRCNet. Actually
    this is being tested with version 2.10.3p3.
 
 Q: Is there a homepage with further information and downloads?
-A: Yes. Please visit <http://arthur.ath.cx/~alex/ngircd/>.
+A: Yes. Please visit <http://ngircd.barton.de/>.
 
 Q: Why should I use ngIRCd instead of the original one?
 A: ngIRCd offers several benefits: no problems with dynamic IPs, easy to
@@ -49,27 +49,42 @@ A: Most probably you are using version 1.5 of GNU automake which seems to be
    version 1.6 of GNU automake.
    (If you are using Debian 3.0 "Woody" you can try to downgrade to version
    1.4 of GNU automake shipped with this distribution; it should work, too.)
-Q: I cannot connect to remote peers and I use the chroot option. ngircd says:
-   ngircd[2152]: Can't resolve example.com: unknown erroror!
 
-A: On Linux/Glibc with chroot enabled you need to put
-   some libraries inside the chroot as well, notably libnss_dns; maybe others.
-   Unfortunately, even linking ngircd statically does not help this.
-   The only known workaround is to either disable chroot support or
-   link against dietlibc instead of glibc. (tnx to Sebastian Siewior)
 
-
-III. Bugs!?
-~~~~~~~~~~~
+III. Runtime
+~~~~~~~~~~~~
+
+Q: Where is the log file located?
+A: ngIRCd does not write its own log file. Instead, ngIRCd uses
+   syslog(3). Check the files in /var/log/ and/or consult the
+   documentation for your system logger daemon.
+Q: I cannot connect to remote peers when I use the chroot option, the
+   following is logged: "Can't resolve example.com: unknown error!".
+A: On Linux/glibc with chroot enabled you need to put some libraries inside
+   the chroot as well, notably libnss_dns; maybe others. Unfortunately, even
+   linking ngircd statically does not help this. The only known workaround
+   is to either disable chroot support or to link against dietlibc instead
+   of glibc. (tnx to Sebastian Siewior)
+Q: I have added an [Oper] section, how do i log on as IRC operator?
+A: You can use the /OPER command in your IRC client to become an IRC operator.
+   ngIRCd will also log all OPER requests (using syslog), if OPER fails you
+   can look there to determine why it did not work (bad password, unauthorized
+   host mask, etc.)
+Q: I am an IRC operator, but MODE doesn't work!
+A: You need to set 'OperCanUseMode = yes' in ngircd.conf to enable MODE for IRC
+   operators.
+
+IV. Bugs!?
+~~~~~~~~~~
 Q: Is there a list of known bugs and desired feature enhancements?
 A: Yes. Have a look at the bug tracking system (Bugzilla) for ngIRCd located
-   at <http://arthur.ath.cx/bugzilla/ngircd/>. There you can file bug reports
-   and feature requests as well as search the bug database.
+   at <http://ngircd.barton.de/bugzilla/index.cgi>. There you can file bug
+   reports and feature requests as well as search the bug database.
 
 Q: What should I do if I found a bug?
-A: Please file a bug report at <http://arthur.ath.cx/bugzilla/ngircd/>!
+A: Please file a bug report at <http://ngircd.barton.de/bugzilla/index.cgi>!
    The author of the particular component will be notified automagically :-)
 
 
 -- 
-$Id: FAQ.txt,v 1.8 2005/07/07 20:53:35 fw Exp $
+$Id: FAQ.txt,v 1.12 2008/01/02 22:47:58 alex Exp $