Dave Hodgkinson wrote: > 1. On a RH6.0 (yes, ick) box without persistent DBI connections, the > server side of the DBD::mysql connection was successfully closed > (netstat shows nothing), but the client side shows a TIME_WAIT state, > which hangs around for 30 seconds or so before > disappearing. Obviously, using Apache::DBI makes this go away, but > it's disturbing nonetheless. Does this ring any bells?
Dunno about number 2, but 1 is perfectly normal. TIME_WAIT is a condition the OS puts a closed socket into to prevent another app from using the socket, just in case the peer host has any more packets to send to that port. The host that closes the socket will put the old socket into TIME_WAIT. BSD IP stack implementations keep sockets in time_wait for about 30 seconds, others go up to 2 minutes. The duration is called 2MSL (2 * max_segment_lifetime). Don't worry about it and dont mess with it (unless you're consuming 64000+ sockets per 30 seconds, in which case you have other problems to deal with ;-) ~mark
