Most MySQL programs that support option files handle the following options. Because these options affect option-file handling, they must be given on the command line and not in an option file. To work properly, each of these options must be given before other options, with these exceptions:
--print-defaults may be used
immediately after
--defaults-file or
--defaults-extra-file.
On Windows, if the server is started with the
--defaults-file and
--install options,
--install must be first. See
Section 2.3.7.7, “Starting MySQL as a Windows Service”.
When specifying file names, avoid the use of the
~ shell metacharacter because it might not be
interpreted as you expect.
--defaults-extra-file=
file_name
Read this option file after the global option file but (on
Unix) before the user option file. If the file does not exist
or is otherwise inaccessible, an error occurs. (For
information about the order in which option files are used,
see Section 4.2.6, “Using Option Files”.) Before MySQL 5.5.8,
file_name must be the full path
name to the file. As of MySQL 5.5.8, the name is interpreted
relative to the current directory if given as a relative path
name.
Use only the given option file. If the file does not exist or
is otherwise inaccessible, an error occurs. Before MySQL
5.5.8, file_name must be the full
path name to the file. As of MySQL 5.5.8, the name is
interpreted relative to the current directory if given as a
relative path name.
Read not only the usual option groups, but also groups with
the usual names and a suffix of
str. For example, the
mysql client normally reads the
[client] and [mysql]
groups. If the
--defaults-group-suffix=_other
option is given, mysql also reads the
[client_other] and
[mysql_other] groups.
Do not read any option files. If program startup fails due to
reading unknown options from an option file,
--no-defaults can be used to
prevent them from being read.
Print the program name and all options that it gets from option files.