Bug #26775 "!includedir" in my.cnf may change the config block
Submitted: 1 Mar 2007 22:57 Modified: 9 Mar 2007 18:02
Reporter: Christian Hammers (Silver Quality Contributor) (OCA) Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.0.32 OS:
Assigned to: Paul DuBois CPU Architecture:Any
Tags: qc

[1 Mar 2007 22:57] Christian Hammers

The following part in the documentation on 
suggests that every include file can only be used for a predefined config
block although it is possible to add "[mysqld]" at the beginning of such a
config file and thus use it for any block regardless where in the /etc/mysql/my.cnf the !include option was.

However, if you were to use the following lines, the directory /home/mydir/my-dump-options  is checked for option files by mysqldump  only, and not by the server or by any other client applications:

!includedir /home/mydir/my-dump-options

Oh and please don't change the behaviour, only the docs! Limiting the config
files is totally unnecessary.



How to repeat:
# echo "!includedir /etc/mysql/conf.d/" >> /etc/mysql/my.cnf

# cd /etc/mysql/conf.d/

# echo -e "[mysqld]\nold_passwords = true" > old_passwords.cnf
# mysqld --help --verbose | grep ^old-passwords
old-passwords                     TRUE

# echo -e "[mysqld]\nold_passwords = false" > old_passwords.cnf
# mysqld --help --verbose | grep ^old-passwords
old-passwords                     FALSE

Suggested fix:
Add a comment that "[section]" is allowed inside any config file.
[2 Mar 2007 7:16] Valeriy Kravchuk
Thank you for a reasonable documentation request.
[9 Mar 2007 18:02] Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.