commit - b715a5f0615cf5201bf9c2e8d8f83e58e2508362
commit + 5b29518ae59e44ab8ef26a19dc484fa1608d1d0e
blob - 7c6140ff98b08a05bb615594d9b22cb099774fb3
blob + 783b2247ead6d0aef23eea66b6ec323263fdc99e
--- README
+++ README
~~~~~~~~~~~~~~~~~
More documentation can be found in the "doc/" directory and the homepage of
-the ngIRCd: <http://arthur.ath.cx/~alex/ngircd/>.
+the ngIRCd: <http://ngircd.barton.de/>.
V. Download
~~~~~~~~~~~
-The homepage of the ngIRCd is: <http://arthur.ath.cx/~alex/ngircd>; you
-will find the newest information about the ngIRCd and the most recent
-("stable") releases there.
+The homepage of the ngIRCd is: <http://ngircd.barton.de/>; you will find
+the newest information about the ngIRCd and the most recent ("stable")
+releases there.
If you are interested in the latest development versions (which are not
always stable), then please read the section "CVS" on the homepage and
If you find bugs in the ngIRCd (which might be there :-), please report
them at the following URL:
-<http://arthur.ath.cx/~alex/ngircd/#bugs>
+<http://ngircd.barton.de/#bugs>
There you can read about known bugs and limitations, too.
If you have critics, patches or something else, please feel free to post a
-mail to: <alex@barton.de> or <alex@arthur.ath.cx>
+mail to <alex@barton.de>.
--
-$Id: README,v 1.20 2005/06/26 21:54:01 alex Exp $
+$Id: README,v 1.20.2.1 2005/07/09 14:41:39 alex Exp $
blob - ed6b1a350a0e60723293d48bdf906cef42973d0c
blob + 53e0a409395b59ba30b35e70afe9001652081d18
--- doc/FAQ.txt
+++ doc/FAQ.txt
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
1.4 of GNU automake shipped with this distribution; it should work, too.)
-III. Bugs!?
-~~~~~~~~~~~
+III. Runtime
+~~~~~~~~~~~~
+
+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
- 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.7 2003/11/07 21:32:15 alex Exp $
+$Id: FAQ.txt,v 1.7.4.1 2005/07/09 14:41:39 alex Exp $