Database Reference
In-Depth Information
*************************** 4. row ***************************
Id: 11482
User: mstone
Host: mstone_home
db: NULL
Command: Query
Time: 78
State: init
Info: SELECT * FROM `birds`
Progress: 0.000
These are trimmed results, but we can see that
mstone@mstone_home
has an active con-
nection even though we've dropped this user account. We're concerned that he's selecting
data from our databases from his home, even though he no longer works for us and isn't
intending on returning. We can kill this process by executing the following:
KILL
11482
;
Notice that we used the process identification number from the results ofthe
SHOW
PROCESSLIST
statement. The
SHOW PROCESSLIST
statement requires the
PROCESS
privilege, and the
KILL
statementrequires the user account to havethe
SUPER
privilege
to execute it. Now that that session has been killed and his user accounts have been
dropped, he can no longer access our databases. For good measure, we should remove his
account from our server at the operating system level, a topic beyond the scope of this
book.
