FAQ.txt 4.6 KB

  1. ngIRCd - Next Generation IRC Server
  2. (c)2001-2010 by Alexander Barton,
  3. alex@barton.de, http://www.barton.de/
  4. ngIRCd is free software and published under the
  5. terms of the GNU General Public License.
  6. -- FAQ: Frequently Asked Questions --
  7. I. General
  8. ~~~~~~~~~~
  9. Q: Is it possible to link the ngIRCd with non-ngIRCd servers?
  10. A: Yes. ngIRCd is compatible to the original ircd used by IRCNet. Actually
  11. this is being tested with version 2.10.3p3. Please note that newer
  12. versions (2.11.x) aren't compatible any more!
  13. Q: Is there a homepage with further information and downloads?
  14. A: Yes. Please visit <http://ngircd.barton.de/>.
  15. Q: Why should I use ngIRCd instead of the original one?
  16. A: ngIRCd offers several benefits: no problems with dynamic IPs, easy to
  17. configure, open source (GPL), under active development.
  18. II. Compilation
  19. ~~~~~~~~~~~~~~~
  20. Q: I did a "Git checkout" but can't execute ./configure because the script
  21. is missing in the generated directory!?
  22. A: When using development versions via Git, the configure script as well as
  23. the Makefile.in templates must be generated using GNU automake and GNU
  24. autoconf. To simplify this task run the ./autogen.sh script which will
  25. execute the required tools for you; then continue with executing the
  26. ./configure script as usual.
  27. Q: The ./autogen.sh script complains "aclocal: command not found".
  28. A: GNU automake is missing on your system but required for building Git
  29. versions of ngIRCd. Install GNU automake 1.6 or later and try again.
  30. Q: The ./autogen.sh script stops with "autoheader: command not found".
  31. A: GNU autoconf is missing on your system but required for building Git
  32. versions of ngIRCd. Install GNU autoconf 2.52 or later and try again.
  33. Q: The ./autogen.sh script fails and the message "automake: configure.in:
  34. AM_INIT_AUTOMAKE must be used" is displayed.
  35. A: Most probably you are using version 1.5 of GNU automake which seems to be
  36. incompatible to the build system of ngIRCd. Solution: upgrade to at least
  37. version 1.6 of GNU automake.
  38. (If you are using Debian 3.0 "Woody" you can try to downgrade to version
  39. 1.4 of GNU automake shipped with this distribution; it should work, too.)
  40. III. Runtime
  41. ~~~~~~~~~~~~
  42. Q: Where is the log file located?
  43. A: ngIRCd does not write its own log file. Instead, ngIRCd uses syslog(3).
  44. Check the files in /var/log/ and/or consult the documentation for your
  45. system logger daemon.
  46. Q: I cannot connect to remote peers when I use the chroot option, the
  47. following is logged: "Can't resolve example.com: unknown error!".
  48. A: see next question blow ...
  49. Q: When running ngIRCd inside a chroot, no IP addresses can be translated
  50. in DNS names, errors like "Name or service not known" are logged.
  51. A: On Linux/glibc with chroot enabled you need to put some libraries inside
  52. the chroot as well, notably libnss_dns; maybe others. Unfortunately, even
  53. linking ngIRCd statically does not help this. So you can either copy
  54. all the required files into the chroot directory:
  55. $ mkdir -p ./chroot/etc ./chroot/lib
  56. $ cp -a /etc/hosts /etc/resolv.conf /etc/nsswitch.conf ./chroot/etc/
  57. $ cp -a /lib/libresolv* /lib/libnss_* ./chroot/lib/
  58. Or you can try to link ngIRCd against an other C library (like dietlibc)
  59. that doesn't depend on NSS modules and/or these files.
  60. Q: I have added an [Oper] section, how do i log on as IRC operator?
  61. A: You can use the /OPER command in your IRC client to become an IRC operator.
  62. ngIRCd will also log all OPER requests (using syslog), if OPER fails you
  63. can look there to determine why it did not work (bad password, unauthorized
  64. host mask, etc.)
  65. Q: I am an IRC operator, but MODE doesn't work!
  66. A: You need to set 'OperCanUseMode = yes' in ngircd.conf, then IRC operators
  67. can use the MODE command for changing modes even when they are not joined
  68. to the specific channel.
  69. Q: How can I "auto-op" users in channels?
  70. A: ngIRCd can't do this: you would have to use some "IRC Services", like
  71. Atheme (<http://atheme.net/atheme.html>) or Anope (<http://www.anope.org>).
  72. See "doc/Services.txt" for setup instructions.
  73. IV. Bugs!?
  74. ~~~~~~~~~~
  75. Q: Is there a list of known bugs and desired feature enhancements?
  76. A: Yes. Have a look at the bug tracking system (GitHub issues) for ngIRCd located
  77. at <https://github.com/ngircd/ngircd/issues>. There you can file bug
  78. reports and feature requests as well as search the bug database.
  79. Q: What should I do if I found a bug?
  80. A: Please file a bug report at <https://github.com/ngircd/ngircd/issues/new>!
  81. The author will be notified automagically :-)