Problems with MySQL 4.0.20

[Steven Roussey]

We had some servers that were upgraded from 4.0.17/18 to 4.0.20 and had
several problems thereafter:

1. Tables with FTS indices became corrupted, with queries on them causing
segfaults on the servers.

2. BinLog files were getting created with ownership of root, not mysql. Then
Mysql complains that it can not read the file and so goes and creates
another (which is fine and owned by mysql). All slaves to the master then
die with corruption warnings about the master.

3. All servers suddenly have a lot of connection errors:
   Aborted connection 109 to db: 'xyz' user: 'aaa' host: `something.i' (Got
timeout reading communication packets)

4. Thread stack warnings:
   Warning: Asked for 196608 thread stack, but got 126976

Reverting back to 4.0.17/18 fixed everything except one server still reports
#4 (better than all servers reporting it). All FTS tables needed to be
repaired (using the older version -- didn't test or trust the newer one).

-steve--