[MDEV-5958] Inconsitent handling of invalid arguments for mysqld_safe Created: 2014-03-26 Updated: 2014-07-25 Resolved: 2014-07-25 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | 5.5.38, 10.0.12 |
| Fix Version/s: | 5.5.39, 10.0.13 |
| Type: | Bug | Priority: | Major |
| Reporter: | Jean Weisbuch | Assignee: | Sergei Golubchik |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
At the moment, if an invalid parameter is put on the [mysqld_safe] section of my.cnf, it is not parsed, no warning is throwed and mysqld_safe is continuing execution without an error code. Its not consistent with the usual way of handling incorrect variables (abort the execution and throw an error message) on mysqld and tools such as mysqldump. –
–
After applying the patch : the execution of mysqld_safe will abort with an error code of 1 and will throw an error. – |
| Comments |
| Comment by Sergei Golubchik [ 2014-07-23 ] |
|
I won't make mysqld_safe to exit on the unrecognized option — it has a good chance of breaking existing installations. At least on Gentoo the default /etc/mysql/my.cnf contains one unrecognized mysqld_safe option. Let's treat all options as implicitly "loose" — only report an error, but don't abort. |