Bug #60729 | mysqld startup should NOT parse ~/.my.cnf for [mysqld] entries | ||
---|---|---|---|
Submitted: | 2 Apr 2011 5:31 | Modified: | 2 Apr 2011 8:41 |
Reporter: | Simon Mudd (OCA) | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: General | Severity: | S2 (Serious) |
Version: | 5.1 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | [mysqld], ~/my.cnf, mysqld, startup, windmill |
[2 Apr 2011 5:31]
Simon Mudd
[2 Apr 2011 7:56]
Valeriy Kravchuk
What you ask for makes sense, but as current behavior is described and intended, all items (but more clear error message, maybe) are feature requests. We should consider them for 5.6+, but for already released GA versions these changes are hardly possible. Users may rely on ~/.my.cnf usage by all MySQL programs, as documented.
[2 Apr 2011 8:41]
Simon Mudd
Thanks for replying rapidly on this. I understand the desire to not change GA version (hence 5.1 or 5.5). Changing the behaviour in 5.6 (to at least _not_ read the ~/.my.cnf file) would be a reasonable change I believe. Also noted at least for mysql client behaviour while much of the documentation mentions ~/.my.cnf it seems the actual implementation of finding this location is by using $HOME, and not looking up the user's home directory via /etc/passwd or the appropriate system call. That can be confusing as many system set $HOME to / on boot up (I've seen this in Linux) and so mysql clients (and maybe the server don't look in the root user's home directory. Perhaps this behavoiur should be clarified in the documentation as client side behaviour from init created daemons (like puppet) can be behave unexpectedly in these conditions.