mysqld

The SQL daemon (that is, the MySQL server). To use client programs, this program must be running, because clients gain access to databases by connecting to the server. See Section 5.3, “mysqld — The MySQL Server”.

mysqld-max

A version of the server that includes additional features. See Section 5.1.2, “The mysqld-max Extended MySQL Server”.

mysqld_safe

A server startup script. mysqld_safe attempts to start mysqld-max if it exists, and mysqld otherwise. See Section 5.1.3, “mysqld_safe — MySQL Server Startup Script”.

mysql.server

A server startup script. This script is used on systems that use run directories containing scripts that start system services for particular run levels. It invokes mysqld_safe to start the MySQL server. See Section 5.1.4, “mysql.server — MySQL Server Startup Script”.

mysqld_multi

A server startup script that can start or stop multiple servers installed on the system. See Section 5.1.5, “mysqld_multi — Program for Managing Multiple MySQL Servers”.

mysql_install_db

This script creates the MySQL grant tables with default privileges. It is usually executed only once, when first installing MySQL on a system. See Section 2.9.2, “Unix Post-Installation Procedures”.

mysql_fix_privilege_tables

This script is used after an upgrade install operation, to update the grant tables with any changes that have been made in newer versions of MySQL. See Section 2.10.3, “Upgrading the Grant Tables”.

myisamchk

A utility to describe, check, optimize, and repair MyISAM tables. myisamchk is described in Section 5.9.5, “myisamchk — MyISAM Table-Maintenance Utility”.

make_binary_distribution

This program makes a binary release of a compiled MySQL. This could be sent by FTP to /pub/mysql/upload/ on ftp.mysql.com for the convenience of other MySQL users.

mysqlbug

The MySQL bug reporting script. It can be used to send a bug report to the MySQL mailing list. (You can also visit http://bugs.mysql.com/ to file a bug report online. See Section 1.7.1.3, “How to Report Bugs or Problems”.)

For Windows, MySQL binary distributions include both the standard server (mysqld.exe) and the MySQL-Max server (mysqld-max.exe), so you need not get a special distribution. Just use a regular Windows distribution, available at http://dev.mysql.com/downloads/. See Section 2.3, “Installing MySQL on Windows”.

For Linux, if you install MySQL using RPM distributions, use the regular MySQL-server RPM first to install a standard server named mysqld. Then use the MySQL-Max RPM to install a server named mysqld-max. The MySQL-Max RPM presupposes that you have installed the regular server RPM. See Section 2.4, “Installing MySQL on Linux” for more information on the Linux RPM packages.

All other MySQL-Max distributions contain a single server that is named mysqld but that has the additional features included.

--with-server-suffix=-max

This option adds a -max suffix to the mysqld version string.

--with-innodb

This option enables support for the InnoDB storage engine. MySQL-Max servers always include InnoDB support. From MySQL 4.0 onwards, InnoDB is included by default in all binary distributions, so you do not need a MySQL-Max server merely to obtain InnoDB support.

--with-bdb

This option enables support for the Berkeley DB (BDB) storage engine.

--with-blackhole-storage-engine

This option enables support for the BLACKHOLE storage engine.

USE_SYMDIR

This define is enabled to turn on database symbolic link support for Windows. Symbolic link support is available for all Windows servers, so a Max server is not needed to take advantage of this feature.

--with-ndbcluster

This option enables support for the NDB Cluster storage engine. Currently (as of 5.0.16), Cluster is supported on Linux, Solaris, and Mac OS X only. Some users have reported success in using MySQL Cluster built from source on BSD operating systems, but these are not officially supported at this time.

On Linux, the MySQL-Max RPM relies on this mysqld_safe behavior. The RPM installs an executable named mysqld-max, which causes mysqld_safe to automatically use that executable from that point on.

If you install a MySQL-Max distribution that includes a server named mysqld-max, then upgrade later to a non-Max version of MySQL, mysqld_safe still attempts to run the old mysqld-max server. If you perform such an upgrade, you should manually remove the old mysqld-max server to ensure that mysqld_safe runs the new mysqld server.

--help

Display a help message and exit. (Added in MySQL 5.0.3)

--autoclose

(NetWare only) On NetWare, mysqld_safe provides a screen presence. When you unload (shut down) the mysqld_safe NLM, the screen does not by default go away. Instead, it prompts for user input:

*<NLM has terminated; Press any key to close the screen>*

If you want NetWare to close the screen automatically instead, use the --autoclose option to mysqld_safe.

--basedir=path

The path to the MySQL installation directory.

--core-file-size=size

The size of the core file mysqld should be able to create. The option value is passed to ulimit -c.

--datadir=path

The path to the data directory.

--defaults-extra-file=path

The name of an option file to be read in addition to the usual option files. If given, this option must be first.

--defaults-file=path

The name of an option file to be read instead of the usual option files. If given, this option must be first.

--ledir=path

The path to the directory containing the mysqld program. Use this option to explicitly indicate the location of the server.

--log-error=path

Write the error log to the given file. See Section 5.11.1, “The Error Log”.

--mysqld=prog_name

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.

--mysqld-version=suffix

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-version=max, mysqld_safe starts the mysqld-max program in the ledir directory. If the argument to --mysqld-version is empty, mysqld_safe uses mysqld in the ledir directory.

--nice=priority

Use the nice program to set the server's scheduling priority to the given value.

--no-defaults

Do not read any option files. If given, this option must be first.

--open-files-limit=count

The number of files mysqld should be able to open. The option value is passed to ulimit -n. Note that you need to start mysqld_safe as root for this to work properly!

--pid-file=path

The path to the process ID file.

--port=port_num

The port number to use when listening for TCP/IP connections. The port number must be 1024 or higher unless MySQL is run as the root system user.

--skip-character-set-client-handshake

Ignore character set information sent by the client and use the default server character set. (This option makes MySQL behave like MySQL 4.0.)

--socket=path

The Unix socket file to use for local connections.

--timezone=zone

Set the TZ time zone environment variable to the given option value. Consult your operating system documentation for legal time zone specification formats.

--user={user_name | user_id}

Run the mysqld server as the user having the name user_name or the numeric user ID user_id. (“User” in this context refers to a system login account, not a MySQL user listed in the grant tables.)

The server and databases can be found relative to the directory from which mysqld_safe is invoked. For binary distributions, mysqld_safe looks under its working directory for bin and data directories. For source distributions, it looks for libexec and 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 distribution).

If the server and databases cannot be found relative to the working directory, mysqld_safe attempts to locate them by absolute pathnames. Typical locations are /usr/local/libexec and /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 configuration time.

--config-file=name

Specify the name of an alternative option file. This affects where mysqld_multi looks for [mysqldN] option groups. Without this option, all options are read from the usual my.cnf file. The option does not affect where mysqld_multi reads its own options, which are always taken from the [mysqld_multi] group in the usual my.cnf file.

--example

Display a sample option file.

--help

Display a help message and exit.

--log=name

Specify the name of the log file. If the file exists, log output is appended to it.

--mysqladmin=prog_name

The mysqladmin binary to be used to stop servers.

--mysqld=prog_name

The mysqld binary to be used. Note that you can specify mysqld_safe as the value for this option also. The options are passed to mysqld. Just make sure that you have the directory where mysqld is located in your PATH environment variable setting or fix mysqld_safe.

--no-log

Print log information to stdout rather than to the log file. By default, output goes to the log file.

--password=password

The password of the MySQL account to use when invoking mysqladmin. Note that the password value is not optional for this option, unlike for other MySQL programs.

--silent

Disable warnings.

--tcp-ip

Connect to each MySQL server via the TCP/IP port instead of the Unix socket file. (If a socket file is missing, the server might still be running, but accessible only via the TCP/IP port.) By default, connections are made using the Unix socket file. This option affects stop and report operations.

--user=user_name

The username of the MySQL account to use when invoking mysqladmin.

--verbose

Be more verbose.

--version

Display version information and exit.

Make sure that the MySQL account used for stopping the mysqld servers (with the mysqladmin program) has the same username and password for each server. Also, make sure that the account has the SHUTDOWN privilege. If the servers that you want to manage have many different usernames or passwords for the administrative accounts, you might want to create an account on each server that has the same username and password. For example, you might set up a common multi_admin account by executing the following commands for each server:

shell> mysql -u root -S /tmp/mysql.sock -proot_password
mysql> GRANT SHUTDOWN ON *.*
    -> TO 'multi_admin'@'localhost' IDENTIFIED BY 'multipass';

See Section 5.7.2, “How the Privilege System Works”. You have to do this for each mysqld server. Change the connection parameters appropriately when connecting to each one. Note that the host part of the account name must allow you to connect as multi_admin from the host where you want to run mysqld_multi.

The --pid-file option is very important if you are using mysqld_safe to start mysqld (for example, --mysqld=mysqld_safe) Every mysqld should have its own process ID file. The advantage of using mysqld_safe instead of mysqld is that mysqld_safe “guards” its mysqld process and restarts it if the process terminates due to a signal sent using kill -9 or for other reasons, such as a segmentation fault. Please note that the mysqld_safe script might require that you start it from a certain place. This means that you might have to change location to a certain directory before running mysqld_multi. If you have problems starting, please see the mysqld_safe script. Check especially the lines:

----------------------------------------------------------------
MY_PWD=`pwd`
# Check if we are starting this relative (for the binary release)
if test -d $MY_PWD/data/mysql -a -f ./share/mysql/english/errmsg.sys -a \
 -x ./bin/mysqld
----------------------------------------------------------------

See Section 5.1.3, “mysqld_safe — MySQL Server Startup Script”. The test performed by these lines should be successful, or you might encounter problems.

The Unix socket file and the TCP/IP port number must be different for every mysqld.

You might want to use the --user option for mysqld, but in order to do this you need to run the mysqld_multi script as the Unix root user. Having the option in the option file doesn't matter; you just get a warning if you are not the superuser and the mysqld processes are started under your own Unix account.

Important: Make sure that the data directory is fully accessible to the Unix account that the specific mysqld process is started as. Do not use the Unix root account for this, unless you know what you are doing.

Most important: Before using mysqld_multi be sure that you understand the meanings of the options that are passed to the mysqld servers and why you would want to have separate mysqld processes. Beware of the dangers of using multiple mysqld servers with the same data directory. Use separate data directories, unless you know what you are doing. Starting multiple servers with the same data directory does not give you extra performance in a threaded system. See Section 5.12, “Running Multiple MySQL Servers on the Same Machine”.

The MySQL Instance Manager is started with /etc/init.d/mysql script.

The MySQL Instance Manager starts all instances and monitors them.

If a server instance fails the MySQL Instance Manager restarts it.

If the MySQL Instance Manager is shut down (for instance with the /etc/init.d/mysql stop command), all instances are shut down by the MySQL Instance Manager.

--help, -?

Display the help message and exit.

--bind-address=name

Bind address to use for connections.

--default-mysqld-path=name

On Unix, where to look for the MySQL Server binary, if no path was provided in the instance section. Example: default-mysqld-path = /usr/sbin/mysqld

--defaults-file=file_name

Read Instance Manager and MySQL Server settings from the given file. All configuration changes by the Instance Manager will be made to this file. This should be used only as the first option to Instance Manager.

--install

On Windows, install Instance Manager as a Windows service. This option was added in MySQL 5.0.11.

--log=name

The path to the IM log file. This is used with the --run-as-service option.

--monitoring-interval=seconds

Interval to monitor instances in seconds. Instance manager will try to connect to each of monitored instances to check whether they are alive/not hanging. In the case of a failure IM will perform several (in fact many) attempts to restart the instance. One can disable this behavior for particular instances with the nonguarded option in the appropriate instance section. If no value was given, the default of 20 seconds will be used.

--passwd, -P

Prepare entry for passwd file and exit.

--password-file=name

Look for the Instance Manager users and passwords in this file. The default file is /etc/mysqlmanager.passwd.

--pid-file=name

The process ID file to use. By default, this file is named mysqlmanager.pid.

--port=port_num

The port number to use for connections. (The default port number, assigned by IANA, is 2273).

--print-defaults

Print the current defaults and exit. This should be used only as the first option to Instance Manager.

--remove

On Windows, removes Instance Manager as a Windows service. This assumes that Instance Manager has been run with --install previously. This option was added in MySQL 5.0.11.

--run-as-service

Daemonize and start the angel process. The angel process is simple and unlikely to crash. It will restart the IM itself in case of a failure.

--socket=name

On Unix, the socket file to use for the connection. By default, the file is named /tmp/mysqlmanager.sock.

--standalone

On Windows, run Instance Manager in standalone mode. This option was added in MySQL 5.0.13.

--user=name

Username to start and run the mysqlmanager under. It is recommended to run mysqlmanager under the same user account used to run the mysqld server.

--version, -V

Output version information and exit.

mysqld-path = <path-to-mysqld-binary>

The path to the mysqld server binary.

shutdown-delay = seconds

The number of seconds IM should wait for the instance to shut down. The default is 35 seconds. After the delay expires, the IM assumes that the instance is hanging and attempts to kill -9 it. If you use InnoDB with large tables, you should increase this value.

nonguarded

This option should be set if you want to disable IM monitoring functionality for a certain instance.

START INSTANCE <instance_name>

This command will attempt to start an instance:

mysql> START INSTANCE mysqld4;
Query OK, 0 rows affected (0,00 sec)

STOP INSTANCE <instance_name>

This will attempt to stop an instance:

mysql> STOP INSTANCE mysqld4;
Query OK, 0 rows affected (0,00 sec)

SHOW INSTANCES

Show the names of all loaded instances:

mysql> show instances;
+---------------+---------+
| instance_name | status  |
+---------------+---------+
| mysqld3       | offline |
| mysqld4       | online  |
| mysqld2       | offline |
+---------------+---------+
3 rows in set (0,04 sec)

SHOW INSTANCE STATUS <instance_name>

Show the status and the version info of selected instance:

mysql> SHOW INSTANCE STATUS mysqld3;
+---------------+--------+---------+
| instance_name | status | version |
+---------------+--------+---------+
| mysqld3       | online | unknown |
+---------------+--------+---------+
1 row in set (0.00 sec)

SHOW INSTANCE OPTIONS <instance_name>

Show options used by an instance:

mysql> SHOW INSTANCE OPTIONS mysqld3;
+---------------+---------------------------------------------------+
| option_name   | value                                             |
+---------------+---------------------------------------------------+
| instance_name | mysqld3                                           |
| mysqld-path   | /home/cps/mysql/trees/mysql-4.1/sql/mysqld        |
| port          | 3309                                              |
| socket        | /tmp/mysql.sock3                                  |
| pid-file      | hostname.pid3                                     |
| datadir       | /home/cps/mysql_data/data_dir1/                   |
| language      | /home/cps/mysql/trees/mysql-4.1/sql/share/english |
+---------------+---------------------------------------------------+
7 rows in set (0.01 sec)

SHOW <instance_name> LOG FILES

The command provides a listing of all log files used by the instance. The result set contains the path to the log file and the log file size. If no log file path is specified in the configuration file (i.e. log=/var/mysql.log), the IM tries to guess its placement. If the IM is unable to guess the logfile placement you should specify the log file location explicitly.

mysql> SHOW mysqld LOG FILES;
+-------------+------------------------------------+----------+
| Logfile     | Path                               | Filesize |
+-------------+------------------------------------+----------+
| ERROR LOG   | /home/cps/var/mysql/owlet.err      | 9186     |
| GENERAL LOG | /home/cps/var/mysql/owlet.log      | 471503   |
| SLOW LOG    | /home/cps/var/mysql/owlet-slow.log | 4463     |
+-------------+------------------------------------+----------+
3 rows in set (0.01 sec)

SHOW <instance_name> LOG {ERROR | SLOW | GENERAL} size[,offset_from_end]

This command retrieves a portion of the specified log file. Because most users are interested in the latest log messages, the size parameter defines the number of bytes you would like to retrieve starting from the log end. You can retrieve data from the middle of the log file by specifying the optional offset_from_end parameter. The following example retrieves 21 bytes of data, starting 23 bytes from the end of the log file and ending 2 bytes from the end of the log file:

mysql> SHOW mysqld LOG GENERAL 21, 2;
+---------------------+
| Log                 |
+---------------------+
| using password: YES |
+---------------------+
1 row in set (0.00 sec)

SET instance_name.option_name=option_value

This commands edits the specified instance's configuration file to change/add instance options. The IM assumes that the configuration file is located at /etc/my.cnf. You should check that the file exists and has appropriate permissions.

mysql> SET mysqld2.port=3322;
Query OK, 0 rows affected (0.00 sec)

Changes made to the configuration file will not take effect until the MySQL server is restarted. In addition, these changes are not stored in the instance manager's local cache of instance settings until a FLUSH INSTANCES command is executed.

UNSET instance_name.option_name

This command removes an option from an instance's configuration file.

mysql> UNSET mysqld2.port;
Query OK, 0 rows affected (0.00 sec)

Changes made to the configuration file will not take effect until the MySQL server is restarted. In addition, these changes are not stored in the instance manager's local cache of instance settings until a FLUSH INSTANCES command is executed.

FLUSH INSTANCES

This command forces IM to reread the configuration file and to refresh internal structures. This command should be performed after editing the configuration file. This command does not restart instances:

mysql> FLUSH INSTANCES;
Query OK, 0 rows affected (0.04 sec)

Options that affect security: See Section 5.6.3, “Startup Options for mysqld Concerning Security”.

SSL-related options: See Section 5.8.7.6, “SSL Command-Line Options”.

Binary log control options: See Section 5.11.3, “The Binary Log”.

Replication-related options: See Section 6.8, “Replication Startup Options”.

Options specific to particular storage engines: See Section 14.1.1, “MyISAM Startup Options”, Section 14.5.3, “BDB Startup Options”, and Section 14.2.4, “InnoDB Startup Options”.

--help, -?

Display a short help message and exit. Use both the --verbose and --help options to see the full message.

--allow-suspicious-udfs

This option controls whether user-defined functions that have only an xxx symbol for the main function can be loaded. By default, the option is off and only UDFs that have at least one auxiliary symbol can be loaded. This prevents attempts at loading functions from shared object files other than those containing legitimate UDFs. This option was added in version 5.0.3. See Section 24.2.3.6, “User-Defined Function Security Precautions”.

--ansi

Use standard (ANSI) SQL syntax instead of MySQL syntax. See Section 1.8.3, “Running MySQL in ANSI Mode”. For more precise control over the server SQL mode, use the --sql-mode option instead.

--basedir=path, -b path

The path to the MySQL installation directory. All paths are usually resolved relative to this.

--bind-address=IP

The IP address to bind to.

--bootstrap

This option is used by the mysql_install_db script to create the MySQL privilege tables without having to start a full MySQL server.

--console

Write error log messages to stderr and stdout even if --log-error is specified. On Windows, mysqld does not close the console screen if this option is used.

--character-sets-dir=path

The directory where character sets are installed. See Section 5.10.1, “The Character Set Used for Data and Sorting”.

--chroot=path

Put the mysqld server in a closed environment during startup by using the chroot() system call. This is a recommended security measure. Note that use of this option somewhat limits LOAD DATA INFILE and SELECT ... INTO OUTFILE.

--character-set-server=charset

Use charset as the default server character set. See Section 5.10.1, “The Character Set Used for Data and Sorting”.

--core-file

Write a core file if mysqld dies. For some systems, you must also specify the --core-file-size option to mysqld_safe. See Section 5.1.3, “mysqld_safe — MySQL Server Startup Script”. Note that on some systems, such as Solaris, you do not get a core file if you are also using the --user option.

--collation-server=collation

Use collation as the default server collation. See Section 5.10.1, “The Character Set Used for Data and Sorting”.

--datadir=path, -h path

The path to the data directory.

--debug[=debug_options], -# [debug_options]

If MySQL is configured with --with-debug, you can use this option to get a trace file of what mysqld is doing. The debug_options string often is 'd:t:o,file_name'. See Section E.1.2, “Creating Trace Files”.

(DEPRECATED) --default-character-set=charset

Use charset as the default character set. This option is deprecated in favor of --character-set-server. See Section 5.10.1, “The Character Set Used for Data and Sorting”.

--default-collation=collation

Use collation as the default collation. This option is deprecated in favor of --collation-server. See Section 5.10.1, “The Character Set Used for Data and Sorting”.

--default-storage-engine=type

This option is a synonym for --default-table-type.

--default-table-type=type

Set the default table type for tables. See Chapter 14, Storage Engines and Table Types.

--default-time-zone=type

Set the default server time zone. This option sets the global time_zone system variable. If this option is not given, the default time zone is the same as the system time zone (given by the value of the system_time_zone system variable.

--delay-key-write[= OFF | ON | ALL]

How the DELAYED KEYS option should be used. Delayed key writing causes key buffers not to be flushed between writes for MyISAM tables. OFF disables delayed key writes. ON enables delayed key writes for those tables that were created with the DELAYED KEYS option. ALL delays key writes for all MyISAM tables. See Section 7.5.2, “Tuning Server Parameters”. See Section 14.1.1, “MyISAM Startup Options”.

Note: If you set this variable to ALL, you should not use MyISAM tables from within another program (such as from another MySQL server or with myisamchk) when the table is in use. Doing so leads to index corruption.

--des-key-file=file_name

Read the default keys used by DES_ENCRYPT() and DES_DECRYPT() from this file.

--enable-named-pipe

Enable support for named pipes. This option applies only on Windows NT, 2000, XP, and 2003 systems, and can be used only with the mysqld-nt and mysqld-max-nt servers that support named pipe connections.

--exit-info[=flags], -T [flags]

This is a bit mask of different flags you can use for debugging the mysqld server. Do not use this option unless you know exactly what it does!

--external-locking

Enable system locking. Note that if you use this option on a system on which lockd does not fully work (as on Linux), it is easy for mysqld to deadlock. This option previously was named --enable-locking.

Note: If you use this option to enable updates to MyISAM tables from many MySQL processes, you have to ensure that these conditions are satisfied:

The easiest way to ensure this is to always use --external-locking together with --delay-key-write=OFF --query-cache-size=0.

(This is not done by default because in many setups it's useful to have a mixture of the above options.)

--flush

Flush all changes to disk after each SQL statement. Normally MySQL does a write of all changes to disk only after each SQL statement and lets the operating system handle the synching to disk. See Section A.4.2, “What to Do If MySQL Keeps Crashing”.

--init-file=file

Read SQL statements from this file at startup. Each statement must be on a single line and should not include comments.

--innodb-safe-binlog

Adds consistency guarantees between the content of InnoDB tables and the binary log. See Section 5.11.3, “The Binary Log”. This option was removed in MySQL 5.0.3, having been made obsolete by the introduction of XA transaction support.

--language=lang_name, -L lang_name

Client error messages in given language. lang_name can be given as the language name or as the full pathname to the directory where the language files are installed. See Section 5.10.2, “Setting the Error Message Language”.

--large-pages

Some hardware/operating system architectures support memory pages greater than the default (usually 4 KB). The actual implementation of this support depends on the underlying hardware and OS. Applications that perform a lot of memory access may obtain performance improvements by using large pages due to reduced Translation Lookaside Buffer (TLB) misses.

Currently, MySQL supports only the Linux implementation of large pages support (which is called HugeTLB in Linux). We have plans to extend this support to FreeBSD, Solaris and possibly other platforms.

Before large pages can be used on Linux, it is necessary to configure the HugeTLB memory pool. For reference, consult the hugetlbpage.txt file in the Linux kernel source.

This option is disabled by default. It was added in MySQL 5.0.3.

--log[=file], -l [file]

Log connections and queries to this file. See Section 5.11.2, “The General Query Log”. If you don't specify a filename, MySQL uses host_name.log as the filename.

--log-bin=[file]

The binary log file. Log all queries that change data to this file. Used for backup and replication. See Section 5.11.3, “The Binary Log”. It is recommended to specify a filename (see Section A.8.1, “Open Issues in MySQL” for the reason) otherwise MySQL uses host_name-bin as the log file basename.

--log-bin-index[=file]

The index file for binary log filenames. See Section 5.11.3, “The Binary Log”. If you don't specify a filename, and if you didn't specify one in --log-bin, MySQL uses host_name-bin.index as the filename.

--log-bin-trust-function-creators[={0|1}]

With no argument or an argument of 1, this option sets the log_bin_trust_function_creators system variable to 1. With an argument of 0, this option sets the system variable to 0. log_bin_trust_function_creators affects how MySQL enforces restrictions on stored function creation. See Section 17.4, “Binary Logging of Stored Routines and Triggers”.

This option was added in MySQL 5.0.16.

--log-bin-trust-routine-creators[={0|1}]

This is the old name for --log-bin-trust-function-creators. Before MySQL 5.0.16, it also applies to stored procedures, not just stored functions and sets the log_bin_trust_routine_creators system variable. As of 5.0.16, this option is deprecated. It is recognized for backward compatibility but its use results in a warning.

This option was added in MySQL 5.0.6.

--log-error[=file]

Log errors and startup messages to this file. See Section 5.11.1, “The Error Log”. If you don't specify a filename, MySQL uses host_name.err as the filename. If the filename has no extension, an extension of .err is added to the name.

--log-isam[=file]

Log all MyISAM changes to this file (used only when debugging MyISAM).

(DEPRECATED) --log-long-format

Log extra information to whichever of the update log, binary update log, and slow queries log that have been activated. For example, username and timestamp are logged for all queries. This option is deprecated, as it now represents the default logging behavior. (See the description for --log-short-format.) The --log-queries-not-using-indexes option is available for the purpose of logging queries that do not use indexes to the slow query log.

--log-queries-not-using-indexes

If you are using this option with --log-slow-queries, then queries that are not using indexes also are logged to the slow query log. See Section 5.11.4, “The Slow Query Log”.

--log-short-format

Log less information to whichever of the update log, binary update log, and slow queries log that have been activated. For example, the username and timestamp are not logged for queries.

--log-slow-admin-statements

Log slow administrative statements such as OPTIMIZE TABLE, ANALYZE TABLE, and ALTER TABLE to the slow query log.

--log-slow-queries[=file]

Log all queries that have taken more than long_query_time seconds to execute to this file. See Section 5.11.4, “The Slow Query Log”. See the descriptions of the --log-long-format and