I hate to be so rude, but does anyone have an idea? If it's really an obvious answer, please smack me upside the head.
Thanks, -reid Reid Sutherland (mysql) wrote: > Hi, > > I'm using a program that makes many mysql connections. Now sometimes it > leaves a hung mysql process. When I run mysqladmin processlist, the > process looks like this. > > (used my own formatting) > > pid,user,host,db,command,time,state,info > ---------------------------------------- > 28285,sqlusername,localhost,EMPTY,Connect,EMPTY,login,EMPTY > > This processes do not listen to SIGTERM, only SIGKILL. > > Is there anything I can do to prevent these type of connections other > then going into battle with the software that causes them? And yes, > I've specified all the timeout related commands to resonable limits. But > they have no effect and these 'connect' processes can last for > days/weeks until KILLed. > > Any ideas? > > -reid > > __ > mysql-3.23.49 > interactive_timeout=28800 > slave_net_timeout=3600 > wait_timeout=28800 > > > --------------------------------------------------------------------- > 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 > > > --------------------------------------------------------------------- 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
