Table Size Killer?

[ostony]

Mysql recently crashed my Linux box during a cron. Mysql quit responding and then the cron keep opening mysql until it cooked the memory. I rebooted, and now I can't restart mysql, I can't use mysqldump or mysqladmin either. They all just hang.

Could it be possible that the table locked up because it exceeded size limits? I have been able to run myisamchk and it says it fixed some errors, but still mysql will not start. The error logs are really of no help in determining what happened as far as I can tell.

My system info:
Linux 2.2.14-5.0 #1 i686

Mysql:
mysql Ver 10.8 Distrib 3.23.21-beta, for pc-linux-gnu (i686)

My error log tells me this:
[Thu Feb 15 20:26:33 2001] [info] [client 209.196.110.9] (32)Broken pipe: client stopped connection before rflush completed
[Fri Feb 16 06:03:48 2001] [error] (23)Too many open files in system: accept: (client socket)

The mysql error log says this:
mysqld ended on Sun Feb 25 22:16:34 EST 2001
mysqld started on Sun Feb 25 22:16:41 EST 2001
/usr/sbin/mysqld: Can't change dir to '/host/' (Errcode: 2)
010225 22:16:41 Aborting

mysqld ended on Sun Feb 25 22:16:41 EST 2001
mysqld started on Sun Feb 25 22:17:06 EST 2001
Please read "Security" section of the manual to find out how to run mysqld as ro
ot!
010225 22:17:06 Aborting

Any help is appreciated.
Thanks,
Jeff