Mattias:
Yes. In your /etc/my.cnf play with settings listed below. My suggestions are
for heavily used server.
interactive_timeout
--------------------
The number of seconds the server waits for activity on an interactive
connection before closing it. An interactive client is defined as a client
that uses the CLIENT_INTERACTIVE option to mysql_real_connect(). See also
wait_timeout. I'd suggest starting with 300 (5 minutes) and see how it
goes. You may need to go up to 900 (15 minutes) or so. You definitely don't
want the default (28800 - forever :-)
wait_timeout
------------
The number of seconds the server waits for activity on a connection before
closing it. See also interactive_timeout. I'd suggest starting with 180 (3
minutes) and see how it goes. You may need to go up to 600 (10 minutes) or
so. You definitely don't want the default (28800 - :-)
> -----Original Message-----
> From: Mattias Segerdahl [mailto:[EMAIL PROTECTED]]
> Sent: Friday, February 02, 2001 1:17 PM
> To: Mysql
> Subject: Stale mysql queries
>
>
> Hi folks,
>
> I got a strange problem, we're running a webhosting company and
> during peekhours, mysql really hits the cpu peek. I do believe there
> is one or more clients that are running high loads of querys
> without actually closing them, or perhaps even running querys that
> dosn't timeout. Is there any way to make a default timeout on
> querys from the server config file?
>
Jim Beigel
[EMAIL PROTECTED]
740-282-2971 x.5205
---------------------------------------------------------------------
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
