Hello.
I didn't find any bug related to this behaviour. What operation system do
you use? Connect to the server with mysql command line client program and
kill it with the SIGKILL signal. Check the error file to find messages
about aborted connections. Can you reproduce a problem on the latest release
(4.1.9 now)? Try only --log-warnings, without specifying the exact value.
[snip]
We are with mysql 4.0.17-log and we want to use --log-warnings to see aborted
connections
in our errorlog.
We put log_warnings = 2 in our my.cnf and restarted mysql but we did not see
aborted
connections in our errorlog.
We tried --log-warnings = 2 on the command line when we started mysql and
again, we did
not see aborted connections in our errorlog.
We tried --log-warnings on the command line when we started mysql and again,
we did not
see aborted connections in our errorlog.
When I do a mysqladmin variables, I saw log_warnings = ON.
So, how can we set this parameter to be able to see something in our
errorlog ?"Marois, David" <[EMAIL PROTECTED]> wrote:
[snip]
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Gleb Paharenko
/ /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED]
/_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET
<___/ www.mysql.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
