Dan Nelson wrote:
>
> You cannot send signals to individual threads. Signals are delivered
> to the process as a whole rather than to a thread. The only way to
> kill a thread is from within the application itself. Mysql provides
> the "kill " command for this.
Thanks for your reply.
What co
Hi everyone,
'processlist' displays the current list of mysql threads as seen by mysql.
I'm looking for that same list but in real thread PID form. Right now I
need to be able to tell which thread is which at a system level. Then I'm
able to send a SIGKILL to some problem threads.
Is the
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 mysq
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,sqluserna
Alex Pilson wrote:
> I was wondering if anyone knew the "proper" way to restart MySQL on OS X?
>
> I did mysqladmin -p shutdown then safe_mysqld...is this the same as if
> the machine started up?
Not exactly the same. But for intents and purposes it does what you want.
If you want to truly ma
Jay Blanchard wrote:
> [snip all kinds of stuff]
>$query = "SELECT * FROM appl";
> $connection = mysql_connect("linuxsrv", "sameer", "sameer");
> mysql_select_db("rcmms", $connection);
> $result = mysql_query($query, $connection);
> ?>
> I says that mysql_connect
>
> Fatal error: Call
Hi everyone,
I have a rather obscure problem with hung login connections in mysql.
I've set the wait|interactive_timeout to 120 seconds, but it has no
effect.\
If I attempt to `mysqladmin kill `, the process is marked 'killed',
but never goes away.
Now I know the main problem is with the p
