Bug #2481 mysqld crash if started with lower-case-table-names=0 and filesystem case-insen
Submitted: 22 Jan 2004 6:38 Modified: 22 Jan 2004 6:38
Reporter: Guilhem Bichot Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.0.17 OS:Any (all)
Assigned to: CPU Architecture:Any

[22 Jan 2004 6:38] Guilhem Bichot 
Description:
Since 4.0.17, if lower-case-table-names==0 and filesystem is case-insensitive, mysqld prints a warning (and sets lower-case-table-names). But this call to sql_print_error() incidentally locks a non-inited mutex (LOCK_error_log) causing mysqld to crash at startup.

How to repeat:
see description

Suggested fix:
Already fixed by Monty in the coming 4.0.18, on Dec 30th 2003.
I document it here to be able to reference it in the manual (a user got this bug)à.
[22 Jan 2004 6:38] Guilhem Bichot 
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
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Fixed in ChangeSet 1.1673 2003/12/30 13:14:21 monty@mysql.com