Bug #19538 | Doesn't report protection error on my.cnf carries on with defaults | ||
---|---|---|---|
Submitted: | 4 May 2006 15:48 | Modified: | 5 Dec 2007 18:55 |
Reporter: | Kerry Gibbings | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: General | Severity: | S4 (Feature request) |
Version: | 4.1.14-log, 5.0bk | OS: | Any (OpenVMS, linux) |
Assigned to: | CPU Architecture: | Any |
[4 May 2006 15:48]
Kerry Gibbings
[5 May 2006 10:07]
Hartmut Holzgraefe
verified with current 5.0 on linux, i can see an EACCESS error in the strace log when starting the server as user "mysql" with a my.cnf only readable by "root", but nothing is shown about it in the error log
[7 Jan 2007 4:14]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/17704 ChangeSet@1.2367, 2007-01-07 05:13:45+01:00, kent@mysql.com +1 -0 default.c: If config file exists but can't be opened, exit with an error message (bug#19538)
[15 Jan 2007 17:44]
Kent Boortz
Patch need to be extended in such a way it has the same behaviour on Windows and Unix. That if a file "exists" but is not readable, it gives a fatal error. Also set it to "feature request", as this is about making it easier to detect a configuration problem.