Use log_error
file and datadir
from mysql_info settings instead of variables mysql_datadir
and mysql_hardening_log_file
#478
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed in PR #477, this PR changes the handling with the log_error file.
The log_error file from mysql_info
mysql_settings.settings.log_error
is used instead of default variablemysql_hardening_log_file
.As drawback, when changing
log_error
option usingmysql_hardening_options
, this new file will not be checked, as the configuration inmysql_hardening_mysql_hardening_conf_file
happens after checking the permissions of the log_error file (but this also was the case when using the default variable).So when changing the setting
log_error
this must be done before running mysql-hardening or run mysql-hardening twice.