mysqld_safe is the recommended way to start a mysqld server on Unix and NetWare. mysqld_safe adds some safety features such as restarting the server when an error occurs and logging runtime information to an error log file. Descriptions of error logging and NetWare-specific behaviors are given later in this section.
In MySQL 5.1.20 (only), the default error logging behavior
with mysqld_safe is to write errors to
syslog on systems that support the
logger program. This differs from the
default behavior of writing an error log file for other
mysqld_safe tries to start an executable
named mysqld. To override the default
behavior and specify explicitly the name of the server you want
to run, specify a
to mysqld_safe. You can also use
--ledir to indicate the
directory where mysqld_safe should look for
Options unknown to mysqld_safe are passed to
mysqld if they are specified on the command
line, but ignored if they are specified in the
[mysqld_safe] group of an option file. See
Section 4.2.6, “Using Option Files”.
mysqld_safe reads all options from the
[mysqld_safe] sections in option files. For
example, if you specify a
like this, mysqld_safe will find and use the
For backward compatibility, mysqld_safe also
[safe_mysqld] sections, but to be
current you should rename such sections to
mysqld_safe supports the options in the following list. It also reads option files and supports the options for processing them described at Section 4.2.7, “Command-Line Options that Affect Option-File Handling”.
|--autoclose||On NetWare, mysqld_safe provides a screen presence|
|--basedir||Path to MySQL installation directory|
|--core-file-size||Size of core file that mysqld should be able to create|
|--datadir||Path to data directory|
|--defaults-extra-file||Read option file in addition to usual option files|
|--defaults-file||Read only named option file|
|--help||Display help message and exit|
|--ledir||Path to directory where server is located|
|--log-error||Write error log to named file|
|--mysqld||Name of server program to start (in ledir directory)|
|--mysqld-version||Suffix for server program name|
|--nice||Use nice program to set server scheduling priority|
|--no-defaults||Read no option files|
|--open-files-limit||Number of files that mysqld should be able to open|
|--pid-file||Path name of process ID file|
|--port||Port number on which to listen for TCP/IP connections|
|--skip-kill-mysqld||Do not try to kill stray mysqld processes|
|--skip-syslog||Do not write error messages to syslog; use error log file||5.1.20|
|--socket||Socket file on which to listen for Unix socket connections|
|--syslog||Write error messages to syslog||5.1.20|
|--syslog-tag||Tag suffix for messages written to syslog||5.1.21|
|--timezone||Set TZ time zone environment variable to named value|
|--user||Run mysqld as user having name user_name or numeric user ID user_id|
Display a help message and exit.
*<NLM has terminated; Press any key to close the screen>*
The path to the MySQL installation directory.
The size of the core file that mysqld should be able to create. The option value is passed to ulimit -c.
The path to the data directory.
The name of an option file to be read in addition to the usual option files. This must be the first option on the command line if it is used. If the file does not exist or is otherwise inaccessible, the server will exit with an error.
The name of an option file to be read instead of the usual option files. This must be the first option on the command line if it is used.
If mysqld_safe cannot find the server, use this option to indicate the path name to the directory where the server is located.
Write the error log to the given file. See Section 5.2.2, “The Error Log”.
The name of the server program (in the
ledir directory) that you want to start.
This option is needed if you use the MySQL binary
distribution but have the data directory outside of the
binary distribution. If mysqld_safe
cannot find the server, use the
--ledir option to
indicate the path name to the directory where the server is
This option is similar to the
--mysqld option, but you
specify only the suffix for the server program name. The
basename is assumed to be mysqld. For
example, if you use
mysqld_safe starts the
mysqld-debug program in the
ledir directory. If the argument to
empty, mysqld_safe uses
mysqld in the
nice program to set the server's
scheduling priority to the given value.
Do not read any option files. This must be the first option on the command line if it is used.
The number of files that mysqld should be able to open. The option value is passed to ulimit -n.
You must start mysqld_safe as
root for this to function properly.
The path name of the process ID file.
The port number that the server should use when listening
for TCP/IP connections. The port number must be 1024 or
higher unless the server is started by the
root system user.
Do not try to kill stray mysqld processes at startup. This option works only on Linux.
The Unix socket file that the server should use when listening for local connections.
--syslog causes error
messages to be sent to
syslog on systems
that support the logger program.
--skip-syslog suppresses the use of
syslog; messages are written to an error
log file. These options were added in MySQL 5.1.20.
syslog is used, the
daemon.err syslog facility/severity is
used for all log messages.
For logging to
syslog, messages from
mysqld_safe and mysqld
are written with identifiers of
mysqld, respectively. To specify a suffix
for the identifiers, use
which modifies the identifiers to be
This option was added in MySQL 5.1.21.
TZ time zone environment variable
to the given option value. Consult your operating system
documentation for legal time zone specification formats.
Run the mysqld server as the user having
user_name or the numeric
(“User” in this context refers to a system
login account, not a MySQL user listed in the grant tables.)
If you execute mysqld_safe with the
to name an option file, the option must be the first one given
on the command line or the option file will not be used. For
example, this command will not use the named option file:
Instead, use the following command:
The mysqld_safe script is written so that it normally can start a server that was installed from either a source or a binary distribution of MySQL, even though these types of distributions typically install the server in slightly different locations. (See Section 2.1.4, “Installation Layouts”.) mysqld_safe expects one of the following conditions to be true:
The server and databases can be found relative to the
working directory (the directory from which
mysqld_safe is invoked). For binary
distributions, mysqld_safe looks under
its working directory for
data directories. For source
distributions, it looks for
var directories. This condition should
be met if you execute mysqld_safe from
your MySQL installation directory (for example,
/usr/local/mysql for a binary
If the server and databases cannot be found relative to the
working directory, mysqld_safe attempts
to locate them by absolute path names. Typical locations are
/usr/local/var. The actual locations
are determined from the values configured into the
distribution at the time it was built. They should be
correct if MySQL is installed in the location specified at
Because mysqld_safe tries to find the server and databases relative to its own working directory, you can install a binary distribution of MySQL anywhere, as long as you run mysqld_safe from the MySQL installation directory:
If mysqld_safe fails, even when invoked from
the MySQL installation directory, specify the
--datadir options to
indicate the directories in which the server and databases are
located on your system.
As of MySQL 5.1.20, there are several mysqld_safe options for controlling the destination of these messages:
Write error messages to the named error file.
--syslog: Write error
syslog on systems that
support the logger program.
If none of these options is given, the default is
In MySQL 5.1.20 only, the default is
--syslog. This differs
from logging behavior for other versions of MySQL, for which
the default is to write messages to the default error log
When mysqld_safe writes a message, notices go
to the logging destination (
syslog or the
error log file) and
stdout. Errors go to the
logging destination and
Before MySQL 5.1.20, error logging is controlled only with the
--log-error option. If it is
given, messages go to the named error file. Otherwise, messages
go to the default error file.
Normally, you should not edit the mysqld_safe
script. Instead, configure mysqld_safe by
using command-line options or options in the
[mysqld_safe] section of a
my.cnf option file. In rare cases, it might
be necessary to edit mysqld_safe to get it to
start the server properly. However, if you do this, your
modified version of mysqld_safe might be
overwritten if you upgrade MySQL in the future, so you should
make a copy of your edited version that you can reinstall.
On NetWare, mysqld_safe is a NetWare Loadable Module (NLM) that is ported from the original Unix shell script. It starts the server as follows:
Runs a number of system and option checks.
Runs a check on
Provides a screen presence for the MySQL server.
Starts mysqld, monitors it, and restarts it if it terminates in error.
Sends error messages from mysqld to the
file in the data directory.
Sends mysqld_safe screen output to the
file in the data directory.