I've been through the bug database a couple of times, and scanned through the list archives before joining, but haven't exactly found anything that matches what is happening in my case.
First, dirty details: I am running MySQL 3.23.33, Apache 1.3.19, and PHP 4.0.6 under an RH system on kernel 2.2.19. PHP running as a module in Apache. I am having a little quirk with persistant connections with MySQL. The connections themselves work; However, after a while when the connections time out, they don't seem to be closing all the way. For instance, right now if I do a netstat, among some other connections I get: Proto Recv-Q Send-Q Local Address tcp 1 0 burner.com:4848 burner.com:mysql CLOSE This has been there and been in "CLOSE" state all day. It was there yesterday. It will be there tomorrow. MySQL has terminated the connection as far as it cares (if I "mysqladmin processlist", no connections show up.) Indeed, if I shut down the MySQL server, the socket remains. Only if I shut down Apache will it ever go away. So, if left going for awhile, tons of these dead sockets will pile up. Before I post a bug report, anyone have any ideas? : Bob Maple (Brazilian) : When love is gone, there's always justice. : : bobm at burner dot com : And when justice is gone, there's always : : : force. And when force is gone, there's : : http: burner.com : always Mom. Hi, Mom! - Laurie Anderson : -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
