Bug #44846 | ndb_config should not read from my.cnf if specified config file can't be found | ||
---|---|---|---|
Submitted: | 13 May 2009 13:22 | Modified: | 20 May 2009 10:14 |
Reporter: | Magnus Blåudd | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
Version: | 6.3 | OS: | Any |
Assigned to: | Magnus Blåudd | CPU Architecture: | Any |
[13 May 2009 13:22]
Magnus Blåudd
[13 May 2009 13:25]
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/73943
[13 May 2009 14:10]
Bugs System
Pushed into 5.1.34-ndb-6.3.25 (revid:magnus.blaudd@sun.com-20090513132521-uke34335n7c615bs) (version source revid:magnus.blaudd@sun.com-20090513132521-uke34335n7c615bs) (merge vers: 5.1.34-ndb-6.3.25) (pib:6)
[13 May 2009 14:11]
Bugs System
Pushed into 5.1.34-ndb-7.0.6 (revid:magnus.blaudd@sun.com-20090513133517-l7vb65braweonf43) (version source revid:magnus.blaudd@sun.com-20090513133418-vwxaxw18y4gqlpmy) (merge vers: 5.1.34-ndb-7.0.6) (pib:6)
[20 May 2009 10:14]
Jon Stephens
Documented bug fix in the NDB-6.3.25 and 7.0.6 changelogs as follows: When ndb_config could not find the file referenced by the --config-file option, it tried to read my.cnf instead, then failed with a misleading error message.