In MySQL 3.23.40 there are no more warnings about aborted connections (yay!) and I can see what is actually in the error log. I found a binlog error message even though we do not use replication or the binlog (though this got me thinking that we should use it as it will be replacing the updatelog and has more features). Does anyone know if this is a fluke or something I should be worried about? Thanks! -steve- 010724 14:48:10 mysqld started /usr/local/mysql/bin/mysqld: ready for connections 010724 14:50:40 /usr/local/mysql/bin/mysqld: Binlog closed, cannot RESET MASTER Status information: Current locks: lock: 45cd20dc: read read : 456f8438 (94229:1); lock: 45a8ff64: lock: 452068c4: key_cache status: blocks used: 30857 not flushed: 0 w_requests: 0 writes: 0 r_requests: 7 reads: 5 handler status: read_key: 1 read_next: 0 read_rnd 0 read_first: 0 write: 0 delete 0 update: 0 Table status: Opened tables: 2 Open tables: 2 Open files: 6 Open streams: 0 Sincerely, Steven Roussey Network54.com http://network54.com/?pp=e --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
