Bug #38673 innodb_log_arch_dir variable still in some source distro support files
Submitted: 8 Aug 2008 15:09 Modified: 5 May 2011 12:15
Reporter: Ben Weiner Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Installing Severity:S3 (Non-critical)
Version:5.1.26-rc OS:Any
Assigned to: CPU Architecture:Any
Tags: config, my.cnf, support-files

[8 Aug 2008 15:09] Ben Weiner
The innodb_log_arch_dir variable, removed in 5.0.24, still in the source distribution in support-files/my-medium.cnf (the sample config mentioned in http://dev.mysql.com/doc/refman/5.0/en/quick-install.html)

It is commented out, but the command mysql_install_db will fail if you uncomment all the innodb variables (as I did).

mysql-5.1.26-rc$ grep innodb_log_arch_dir support-files/*
support-files/my-huge.cnf.sh:#innodb_log_arch_dir = @localstatedir@/
support-files/my-large.cnf.sh:#innodb_log_arch_dir = @localstatedir@/
support-files/my-medium.cnf.sh:#innodb_log_arch_dir = @localstatedir@/
support-files/my-small.cnf.sh:#innodb_log_arch_dir = @localstatedir@/

How to repeat:
compile, make, make install.
copy any of these files to /etc/my.cnf:

uncomment all lines in /etc/my.cnf that define an innodb variable.

run mysql_install_db in mysql/bin directory.

Suggested fix:
remove #innodb_log_arch_dir = @localstatedir@/ from relevant source files
[8 Aug 2008 16:14] MySQL Verification Team
Thank you for the bug report.
[14 Jan 2009 2:04] Meiji KIMURA
The patch for this bug is pushed to 6.0.8. (See Bug#38249).

Is there any possibility to modify 5.1.x?
[17 Mar 2009 2:00] Meiji KIMURA
The same patch pushed into 5.1.33.
[5 May 2011 12:15] Joerg Bruehe
Most probably, the changeset fixing this did not mention the bug number in its comment, so it did not get linked here (and did not cause a status change).

Regardless of how and when it was done, the bug got fixed.
It is so minor, and the fix was done so long ago, I close it without asking for documentation.