List:General Discussion« Previous MessageNext Message »
From:Paul DuBois Date:November 28 1999 6:13pm
Subject:Re: orphaned mysql process
View as plain text  
At 9:38 AM -0700 11/28/99, John McDermon wrote:
>Hi All,
>I'm in a bit of a jam.
>I was just browsing the mysql user table on a production database 
>and I lost the terminal connection (risks of using dialup).
>
>So now I'm back on the system, and here is what the process table shows:
>$ ps -ef | grep mysql | grep -v grep | sort -n +1
>     root  1307     1  0  Nov 22  ?         0:00 /bin/sh 
>/home/mysql/mysql/bin/safe_mysqld -l
>     root  1325  1307  0  Nov 22  ?        26:16 
>/homedirs/mysql/mysql/libexec/mysqld --basedir=/homedirs/mys
>    mysql 11531 11528  0 08:41:46 pts/1     0:00 -bash
>    mysql 11543 11531  0 08:41:54 pts/1     0:00 mysql mysql
>    mysql 11694 11664  0 09:15:30 pts/0     0:00 -bash
>
>I don't have a problem killing the older shell (PID 11531), but I'm 
>concerned about killing the mysql process (PID 11543) since it's 
>"connected" to the database.
>
>Will this be a problem? and If so what can I do to minimize the damage?


What is the "damage"?

I'd go ahead and kill the mysql process.  I've never observed any particular
problem with clients being clobbered.  Or you could just leave it; eventually
the server will time out the connection.

-- 
Paul DuBois, paul@stripped
Thread
orphaned mysql processJohn McDermon28 Nov
  • Re: orphaned mysql processVan28 Nov
  • Re: orphaned mysql processPaul DuBois28 Nov