Dropped Connections, Abandoned Queries

Can anyone point to documentation, or pass along some insight on how MySQL
handles dropped connections and abandoned queries?

How does MySQL cope with people/processes that log on and then neglect/fail
to logout properly? Clearly multiple logons to the same user id are
permitted. Do abandoned sessions stack up chewing up system resources or do
they timeout from inactivity?

What happens to queries that are initiated but the requester simply quits
before results are returned?

What happens when a usr:
initiates a slow query
abandons the session (cold!) before results are returned
logs on (again) and reissue the same slow query
over and over and over again!

What are some variables - timeouts and such - that might be associated with
these situations? Other than identifying certain users/abusers and whacking
them upside the head, how does one tweak the MySQL server to cope better.

All comments, experiences, and insights appreciated.
Thomas Bartkus

Thomas Bartkus wrote:
 > Can anyone point to documentation, or pass along some insight on how MySQL
 > handles dropped connections and abandoned queries?

<a style='text-decoration: underline;' href="http://dev.mysql.com/doc/mysql/en/communication-errors.html" target="_blank">http://dev.mysql.com/doc/mysql/en/communication-errors.html</a>

Regards,
Bill K.<!-- ~MESSAGE_AFTER~ -->