1 |
Known Bugs worthy of a mention: |
2 |
-------------------------------------------------------------------------------- |
3 |
|
4 |
1. /MODUNLOAD causes cores: |
5 |
- If a module is modified before being unloaded, /MODUNLOAD (and |
6 |
therefore /MODRELOAD) may cause a core. |
7 |
|
8 |
This problem is caused by the behaviour of the OS, which treats |
9 |
shared libraries differently to executables (modifying the ircd |
10 |
binary whilst it is running would also cause a core, but is denied |
11 |
by the OS). There is no way to fix this at the application level, |
12 |
and fixing the OS to do the right thing is also difficult. |
13 |
|
14 |
A workaround to avoid coring is possible however. To install new |
15 |
modules, first remove or rename the old module, then copy/move the |
16 |
new file into place. /MODUNLOAD will then work successfully. |
17 |
|
18 |
Alternatively, running ./configure with the --disable-shared-modules |
19 |
argument will link all the commands statically, losing the advantages |
20 |
of upgrading at runtime, but reducing the chances of accidentally |
21 |
coring your server. |
22 |
|
23 |
2. Solaris stock 32bit stdio is limited to 256 fds. This breaks when using |
24 |
cryptlinks. |
25 |
|
26 |
BUG REPORTS: If you run this code and encounter problems, you should report |
27 |
the bug on our SourceForge.net bug tracker, which you can find at this URL: |
28 |
|
29 |
https://sourceforge.net/tracker/?atid=409046&group_id=33573&func=browse |
30 |
|
31 |
Please include a gdb backtrace and a copy of your setup.h and ircd.conf with |
32 |
any report (with passwords and other sensitive information masked). |
33 |
|
34 |
For information how to get a gdb backtrace, see INSTALL (near the end of file). |
35 |
|
36 |
-------------------------------------------------------------------------------- |
37 |
$Id$ |