| Bug #61655 | Single quoted paths are not recognized correctly | ||
|---|---|---|---|
| Submitted: | 27 Jun 2011 11:29 | Modified: | 29 Dec 2011 20:01 |
| Reporter: | Holger Thiel | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Enterprise Backup | Severity: | S3 (Non-critical) |
| Version: | 3.5.2, 3.5.4 | OS: | Linux |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | my.cnf quotes | ||
[27 Jun 2011 13:37]
Valeriy Kravchuk
What exact version of MySQL Enterprise Backup do you use?
[27 Jun 2011 13:40]
Holger Thiel
It is version 3.5.2 .
[27 Jun 2011 13:46]
Valeriy Kravchuk
May be related to bug #57824 (that part that quoting does not help).
[8 Jul 2011 11:30]
Sveta Smirnova
Thank you for the report. Verified as described using version 3.5.4 With version 3.6 bug is not repeatable.
[29 Dec 2011 20:01]
Hema Sridharan
This bugs is not reproducible in MEB 3.6.1 (Verified by Jothir) and hence closing it.
Description: The Enterprise Backup has problems with parameters with single quotes ('') in the my.cnf. Single quotes are a correct syntax and should be used for paths with spaces. See also bug #58968. So the Enterprise Backup behaves not correctly. e.g.: datadir = '/DATADIR/instance/data' # path with single quotes datadir = /DATADIR/instance/data # path without single quotes How to repeat: Use ptathes with single quotes on the parameters datadir, innodb_log_group_home_dir, innodb_data_home_dir or innodb_data_file_path Suggested fix: Enterprise Backups should correctly parse the my.cnf.