|
Revision 1330, 1.2 KB
(checked in by shawnw, 7 weeks ago)
|
|
Merge in recent changes from trunk.
|
| Line | |
|---|
| 1 | Bugs that aren't our fault, but might bite people: |
|---|
| 2 | |
|---|
| 3 | Modern: |
|---|
| 4 | |
|---|
| 5 | * You might experience crashes because the default executable stack |
|---|
| 6 | size is too small. An 8 megabyte stack is more than ample. On unix, |
|---|
| 7 | it can be raised with 'ulimit -s 8192'. On Windows, you must use the |
|---|
| 8 | editbin progam that comes with MS development environments to raise |
|---|
| 9 | the stack on a per-executable basis, via 'editbin /STACK:8388608 |
|---|
| 10 | netmush.exe' |
|---|
| 11 | |
|---|
| 12 | * Some IPv6-enabled systems are not configured out of the box to |
|---|
| 13 | tunnel IPv4 connection attempts on the same port to the IPv6 socket |
|---|
| 14 | that is listening. If you can connect to a local game via ::1 but |
|---|
| 15 | not 127.0.0.1 this is likely the issue. On unix systems, a user with |
|---|
| 16 | root privileges can do 'sysctl -w net.inet6.ip6.v6only=0', after |
|---|
| 17 | which you'll have to do a complete shutdown and restart of the mush |
|---|
| 18 | for the change to take effect. The file /etc/sysctl.conf will have |
|---|
| 19 | to be changed too so the change persists across server reboots. |
|---|
| 20 | If that's not practical, you can get an IPv4-only mush by doing |
|---|
| 21 | the following: |
|---|
| 22 | |
|---|
| 23 | % ./configure --disable-ipv6 |
|---|
| 24 | % make |
|---|
| 25 | |
|---|
| 26 | Then do a full @shutdown of the game and run restart. |
|---|
| 27 | |
|---|
| 28 | |
|---|
| 29 | You can browse the bug and suggestion database at |
|---|
| 30 | http://dev.pennmush.org to see more. |
|---|
