[MDEV-12734] mysql_secure_installation does not read configuration file Created: 2017-05-08 Updated: 2020-12-01 |
|
| Status: | Confirmed |
| Project: | MariaDB Server |
| Component/s: | Packaging |
| Affects Version/s: | 10.0, 10.1, 10.2 |
| Fix Version/s: | 10.2 |
| Type: | Bug | Priority: | Major |
| Reporter: | Michaël de groot | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Hi, After tarball installation with different socket path specified, the mysql_secure_installation script does not work. It does not read the socket= parameter in the configruation file (I tried sections server-client, client and mysql). Thanks, |
| Comments |
| Comment by Elena Stepanova [ 2017-05-14 ] |
|
As of 10.2, mysql_secure_installation is just a shell script which has no notion of default locations for configuration files. If you give the path to the file to mysql_secure_installation as a command-line defaults-file, it will be used. I assume you are comparing it to MySQL 5.7 version, where it was re-written to C. I can convert it to a feature request for future versions. |
| Comment by Sergei Golubchik [ 2017-05-24 ] |
|
mysql_secure_installation works fine with a tarball extracted in a non-default location, but only if you specify --basedir. It doesn't hande --defaults-file correctly (it does support it, but it gets its value after loading my.cnf, which is obviously a bug). |
| Comment by Sergei Golubchik [ 2017-05-24 ] |
|
Also mysql_secure_installation is not as good at guessing the basedir as mysqld_safe is. Should be fixed too. |
| Comment by Daniel Black [ 2018-02-04 ] |
|
elenst I think converting into a porting task to get the mysql-5.7+ mysql_secure_installation.c into mariadb-10.3 and then quite a few outstanding mysql_secure_installation bugs will just go away. It also sets a basis for doing future work and enhancements. |