hi
from the manual:
"Aborted_clients : This means that something of the following has happened:
· The client program did not call mysql_close() before exit.
· The client had been sleeping more than wait_timeout or
interactive_timeout without doing any requests. See section ·
· The client program ended abruptly in the middle of the transfer.
When the above happens, the server variable Aborted_clients is incremented.
Aborted_connects is incremented when:
· When a connection packet doesn't contain the right information.
· When the user didn't have privileges to connect to a database.
· When a user uses a wrong password.
· When it takes more than connect_timeout seconds to get a connect
package.
Note that the above could indicate that someone is trying to break into
your database! "
regards
At 14:19 22/08/01, Grigory Bakunov wrote:
>Date |Tue, 21 Aug 2001 10:01:30 -0500
> From |Tony Wells <[EMAIL PROTECTED]>
>
>Hello!
>
>
>TW> Hi all,
>
>TW> I'm running MySQL Ver 3.23.32 for -freebsd4.2 on i386, With PHP4
>TW> compiled statically into Apache 1.3.17. All connections to the database
>TW> are non-persistent connections. It's a pretty busy server, hitting
>TW> about 60 queries per second during peak time. (Although I'm not sure
>TW> that would qualify as busy on this list. :)
>
>TW> I was wondering about a couple of the variables reported in 'mysqladmin
>TW> extended-status', specifically 'aborted clients' and 'aborted
>TW> connections' and what the difference between the two are.
>
>TW> We get a lot of these, but I'm guessing this is just an artifact of
>TW> users hitting the 'stop' button before a page finishes loading, or maybe
>TW> not.
>
>TW> The other question I have is after a period of time, maybe about a
>TW> month, connections to the database will return an error 'Too many errors
>TW> connecting to database, use mysqladmin flush-hosts ...' or something to
>TW> that effect. (It's been awhile since it's happened.) Flushing the hosts
>TW> solves the problem but I was wanting to do garbage collection on these
>TW> connections to prevent this, and I was wondering what the best method
>TW> would be.
>
>In short words you need to close all opened connections in your script.
>For example if you use in script
>$link = mysql_connect (...);
>you must close connection by
>mysql_close($link);
>in other case you have 'abborted connections'
>
>___________________________________________________________________
>For technical support contracts, visit https://order.mysql.com/
>This email is sponsored by SWSoft, http://www.asplinux.ru/
> __ ___ ___ ____ __
> / |/ /_ __/ __/ __ \/ / Grigory Bakunov <[EMAIL PROTECTED]>
> / /|_/ / // /\ \/ /_/ / /__ MySQL AB / SWSoft
>/_/ /_/\_, /___/\___\_\___/
> <___/ www.mysql.com
>
>
>---------------------------------------------------------------------
>Before posting, please check:
> http://www.mysql.com/manual.php (the manual)
> http://lists.mysql.com/ (the list archive)
>
>To request this thread, e-mail <[EMAIL PROTECTED]>
>To unsubscribe, e-mail
><[EMAIL PROTECTED]>
>Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
