commit - 1eca0aea4f37cd1dff9075a9d969096784e96fd0
commit + a874c26c254e044bf10276d27ec8a9a19ce44c9b
blob - a44fb71785590282b9129b96623260cbb0fe07b6
blob + c0dc07855ec569c49e25da08716e91cb0cf17083
--- doc/FAQ.txt
+++ doc/FAQ.txt
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. Runtime
+~~~~~~~~~~~~
-III. Bugs!?
-~~~~~~~~~~~
+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)
+
+
+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
--
-$Id: FAQ.txt,v 1.8 2005/07/07 20:53:35 fw Exp $
+$Id: FAQ.txt,v 1.9 2005/07/08 12:40:09 alex Exp $