Using Mysql.server With My.cnf To Start Mysqld_safe/mysqld
(Doc ID 2227622.1)
Last updated on FEBRUARY 11, 2019
Applies to:MySQL Server - Version 5.6 to 8.0 [Release 5.6 to 8.0]
Information in this document applies to any platform.
On 5.6.35 version, Installation and Upgrading
Using mysql.server with my.cnf to start mysqld_safe/mysqld
Incompatible Change: These changes were made to mysqld_safe:
Unsafe use of rm and chown in mysqld_safe could result in privilege escalation. chown now can be used only when the target directory is /var/log. An incompatible change is that if the directory for the Unix socket file is missing, it is no longer created; instead, an error occurs. Due to these changes, /bin/bash is required to run mysqld_safe on Solaris. /bin/sh is still used on other Unix/Linux platforms.
The --ledir option now is accepted only on the command line, not in option files.
mysqld_safe ignores the current working directory.
Other related changes:
Initialization scripts that invoke mysqld_safe pass --basedir explicitly.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document