| 1 |
Known Bugs worthy of a mention: |
| 2 |
-------------------------------------------------------------------------------- |
| 3 |
|
| 4 |
1. Issues with server hostmasking. |
| 5 |
- If for example the new servername is blah.blah.blah.nl, the following |
| 6 |
servernames will be checked, in this order: *.blah.blah.nl, *.blah.nl, |
| 7 |
*.nl, one of which will match the host-masked server they are |
| 8 |
connecting behind. This will be accepted by the host-masked server it |
| 9 |
is connected behind, but when it reaches the server the host-masked |
| 10 |
server is connected to, the find_server will match, so the host-masked |
| 11 |
server will be dropped. |
| 12 |
--> This corrected? |
| 13 |
|
| 14 |
2. /MODUNLOAD causes cores: |
| 15 |
- If a module is modified before being unloaded, /MODUNLOAD (and |
| 16 |
therefore /MODRELOAD) may cause a core. |
| 17 |
|
| 18 |
This problem is caused by the behaviour of the OS, which treats |
| 19 |
shared libraries differently to executables (modifying the ircd |
| 20 |
binary whilst it is running would also cause a core, but is denied |
| 21 |
by the OS). There is no way to fix this at the application level, |
| 22 |
and fixing the OS to do the right thing is also difficult. |
| 23 |
|
| 24 |
A workaround to avoid coring is possible however. To install new |
| 25 |
modules, first remove or rename the old module, then copy/move the |
| 26 |
new file into place. /MODUNLOAD will then work successfully. |
| 27 |
|
| 28 |
Alternatively, running ./configure with the --disable-shared-modules |
| 29 |
argument will link all the commands statically, losing the advantages |
| 30 |
of upgrading at runtime, but reducing the chances of accidentally |
| 31 |
coring your server. |
| 32 |
|
| 33 |
3. Problem with msgfmt command building custom msgs using gettext |
| 34 |
- Please ensure you are using GNU gettext version 0.10.35. |
| 35 |
Other versions are untested, and some are known to be |
| 36 |
incompatible. |
| 37 |
|
| 38 |
4. Problems with quote set msglocale not working on linux. |
| 39 |
This seems to be a linux problem, /quote set msglocale will sometimes |
| 40 |
get "undone" when a new client connects. The server will also sometimes |
| 41 |
not correctly set the locale from ircd.conf on startup. |
| 42 |
|
| 43 |
The solution is if a locale is needed, to have the message_locale="x" |
| 44 |
in ircd.conf, and then rehash to make it take effect. A rehash after |
| 45 |
startup will also need to be performed to set the locale. |
| 46 |
|
| 47 |
5. When updating a message file, in certain unknown situations it will core |
| 48 |
if the file in use is being accessed. To prevent this from happening, |
| 49 |
use '/quote SET MSGLOCALE standard' BEFORE issuing make install. When |
| 50 |
the file is installed, you can SET MSGLOCALE back to the language that |
| 51 |
was just updated. |
| 52 |
|
| 53 |
6. PRIVMSG/NOTICE oper@server :message |
| 54 |
This translates into a WALLOPS message, broken. |
| 55 |
|
| 56 |
7. KNOCK and channel mode +p are inconsistant with Hybrid 6. |
| 57 |
|
| 58 |
8. TCP Resolver does not function properly and is disabled. |
| 59 |
The only time you are likely to hit the TCP resolver is for queries |
| 60 |
over 512 bytes. |
| 61 |
|
| 62 |
BUG REPORTS: If you run this code and encounter problems, you must report |
| 63 |
the bug in by E-MAIL to ircd-hybrid@the-project.org. |
| 64 |
|
| 65 |
Please include a gdb backtrace and a copy of your config.h and ircd.conf |
| 66 |
with any report (with passwords and other sensitive information masked). |
| 67 |
|
| 68 |
-------------------------------------------------------------------------------- |
| 69 |
$Id: BUGS,v 7.45 2001/12/02 15:00:48 leeh Exp $ |
