> I'm not sure if I understand what you mean? Let's say Joe User does $ echo "[SOMETHING DUMB;]"|mysql which seems to take a long time, so hits ^C and does $ logout #and leaves for a weekend at the beach. Meanwhile the CPU is still pegged at 100% processing his dumb query even though he has already hung up. Indeed, maybe for the rest of the day[s] the CPU will be pegged at 100%. Until one day perhaps the system administrator notices. > In this case you don't have to restart the server but can use > "SHOW PROCESSLIST" and "KILL 10" etc to kill the offending query. I see in 13.5.5.3 `KILL' Syntax there is lots of ways. I will try that next time my query loops, however Joe has left the office and the CPU is stuck at 100% > What you ask is that this should be done automatically by the server? Perhaps /usr/bin/mysql, upon getting the ^C, could tell the server, "Yo, for your information, I'm dying. Just wanted to let you know." Whereupon it would kill Joe's dumb query.
Maybe checking first if he had mysql-nohup'ed (I.e., maybe there is something like nohup(1) in the mysql language) his job. All I have done so far with databases is read-only queries, so maybe this is inappropriate for commands the UPDATE tables. OK, maybe each user should know about SHOW PROCESSLIST and KILL. And keep an eye on the CPU meter, before leaving for lunch. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
