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
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
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.9 2005/07/08 12:40:09 alex Exp $
+$Id: FAQ.txt,v 1.12 2008/01/02 22:47:58 alex Exp $