Bug #5303 Windows --log-error option doesn't work correctly
Submitted: 30 Aug 2004 21:18 Modified: 2 Nov 2004 17:42
Reporter: Paul DuBois Email Updates:
Status: Closed Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.1 OS:Windows (WIndows)
Assigned to: Reggie Burnett CPU Architecture:Any

[30 Aug 2004 21:18] Paul DuBois
On Windows:

When you specify --log-error without an option value, the server
is supposed to use host_name.err in the data directory as the error
log name.  When you specify --log-error=xxx, the server is supposed
to use xxx as the error log name (possibly adding an .err suffix, in
the case that the name includes no suffix.)

What actually happens is that the server does create an error log
named as described in the previous paragraph. However, the only
message that actually goes into the error log is the "InnoDB:
started" message.  All other diagnostic output goes to the file
mysql.err in the data directory.  In other words, the server seems
to believe that it should use the error log behavior that was
standard before MySQL 4.0.10! :-)

How to repeat:
See above.
[30 Aug 2004 21:49] MySQL Verification Team
Thank you for the bug report I was able to repeat on 4.1.3b.
The 4.0.20 behaves as expected.
[3 Sep 2004 0:22] Reggie Burnett
I have been  unable to reproduce this.  I have an email into Paul to find out more.
[3 Sep 2004 1:24] Paul DuBois
It's easy to reproduce. First make sure your data directory
has no *.err files, so you know that the following commands
create any that exist afterward.  Then cd into the bin
directory and start the server like this:

mysqld-opt --log-error=abc

This results in an abc.err file and mysql.err file in the data

By the way, I just tried it with 4.1.4-gamma (using mysqld)
and the same behavior occurs.
[2 Nov 2004 17:42] Reggie Burnett
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at