@@ -25,8 +25,7 @@ mysqld_multi \- manage multiple MySQL servers
\fBmysqld_multi\fR
is designed to manage several
\fBmysqld\fR
processes that listen for connections on different Unix socket files and TCP/IP ports\&. It can start or stop servers, or report their current status\&. The MySQL Instance Manager is an alternative means of managing multiple servers (see
\fBmysqlmanager\fR(8))\&.
processes that listen for connections on different Unix socket files and TCP/IP ports\&. It can start or stop servers, or report their current status\&.
.PP
\fBmysqld_multi\fR
searches for groups named
...
...
@@ -43,9 +42,7 @@ can be any positive integer\&. This number is referred to in the following discu
to specify which servers you want to start, stop, or obtain a status report for\&. Options listed in these groups are the same that you would use in the
[mysqld]
group used for starting
\fBmysqld\fR\&. (See, for example,
Section\ \&2.13.1.2, \(lqStarting and Stopping MySQL Automatically\(rq\&.) However, when using multiple servers, it is necessary that each one use its own value for options such as the Unix socket file and TCP/IP port number\&. For more information on which options must be unique per server in a multiple\-server environment, see
Section\ \&5.6, \(lqRunning Multiple MySQL Servers on the Same Machine\(rq\&.
\fBmysqld\fR\&. However, when using multiple servers, it is necessary that each one use its own value for options such as the Unix socket file and TCP/IP port number\&.
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\&.
Connect to the MariaDB server(s) via the TCP/IP port instead of the UNIX socket\&. This affects stopping
and reporting. If a socket file is missing, the server may still be running, but can be accessed only
via the TCP/IP port\&. By default connecting is done via the UNIX socket\&. This option affects
stop and report operations\&.
.RE
.sp
.RS 4
...
...
@@ -437,7 +386,7 @@ operations\&.
.\" user option: mysqld_multi
\fB\-\-user=\fR\fB\fIuser_name\fR\fR
.sp
The user name of the MySQL account to use when invoking
The user name of the MariaDB account to use when invoking
\fBmysqladmin\fR\&.
.RE
.sp
...
...
@@ -496,8 +445,9 @@ servers with the same data directory\&. Use separate data directories, unless yo
\fIknow\fR
what you are doing\&. Starting multiple servers with the same data directory does
\fInot\fR
give you extra performance in a threaded system\&. See
Section\ \&5.6, \(lqRunning Multiple MySQL Servers on the Same Machine\(rq\&.
give you extra performance in a threaded system\&.
.sp .5v
.RE
.RE
.sp
.RS 4
...
...
@@ -508,19 +458,7 @@ Section\ \&5.6, \(lqRunning Multiple MySQL Servers on the Same Machine\(rq\&.
.sp -1
.IP \(bu 2.3
.\}
.if n \{\
.sp
.\}
.RS 4
.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1
.br
.ps +1
\fBImportant\fR
.ps -1
.br
Make sure that the data directory for each server is fully accessible to the Unix account that the specific
\fBImportant\fR: Make sure that the data directory for each server is fully accessible to the Unix account that the specific
\fBmysqld\fR
process is started as\&.
\fIDo not\fR
...
...
@@ -528,8 +466,7 @@ use the Unix
\fIroot\fR
account for this, unless you
\fIknow\fR
what you are doing\&. See
Section\ \&5.3.6, \(lqHow to Run MySQL as a Normal User\(rq\&.
what you are doing\&.
.sp .5v
.RE
.RE
...
...
@@ -542,7 +479,7 @@ Section\ \&5.3.6, \(lqHow to Run MySQL as a Normal User\(rq\&.
.sp -1
.IP \(bu 2.3
.\}
Make sure that the MySQL account used for stopping the
Make sure that the MariaDB account used for stopping the
\fBmysqld\fR
servers (with the
\fBmysqladmin\fR
...
...
@@ -565,10 +502,7 @@ mysql> \fBGRANT SHUTDOWN ON *\&.*\fR
.RE
.\}
.sp
See
Section\ \&5.4, \(lqThe MySQL Access Privilege System\(rq\&. You have to do this for each
\fBmysqld\fR
server\&. Change the connection parameters appropriately when connecting to each one\&. Note that the host name part of the account name must allow you to connect as
Change the connection parameters appropriately when connecting to each one\&. Note that the host name part of the account name must allow you to connect as
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
script is written so that it normally can start a server that was installed from either a source or a binary distribution of MariaDB, even though these types of distributions typically install the server in slightly different locations\&.
\fBmysqld_safe\fR
expects one of the following conditions to be true:
.sp
...
...
@@ -537,7 +640,7 @@ and
var
directories\&. This condition should be met if you execute
\fBmysqld_safe\fR
from your MySQL installation directory (for example,
from your MariaDB installation directory (for example,
/usr/local/mysql
for a binary distribution)\&.
.RE
...
...
@@ -555,14 +658,14 @@ If the server and databases cannot be found relative to the working directory,
attempts to locate them by absolute path names\&. 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\&.
/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 MariaDB is installed in the location specified at configuration time\&.
.RE
.PP
Because
\fBmysqld_safe\fR
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
tries to find the server and databases relative to its own working directory, you can install a binary distribution of MariaDB anywhere, as long as you run
fails, even when invoked from the MySQL installation directory, you can specify the
fails, even when invoked from the MariaDB installation directory, you can specify the
\fB\-\-ledir\fR
and
\fB\-\-datadir\fR
...
...
@@ -592,7 +695,7 @@ arranges for error (and notice) messages from itself and from
\fBmysqld\fR
to go to the same destination\&.
.PP
As of MySQL 5\&.1\&.20, there are several
There are several
\fBmysqld_safe\fR
options for controlling the destination of these messages:
.sp
...
...
@@ -652,9 +755,6 @@ If none of these options is given, the default is
.ps -1
.br
.PP
In MySQL 5\&.1\&.20
\fIonly\fR, the default is
\fB\-\-syslog\fR\&. This differs from logging behavior for other versions of MySQL, for which the default is to write messages to the default error log file\&.
.sp .5v
.RE
.PP
...
...
@@ -673,10 +773,6 @@ or the error log file) and
stdout\&. Errors go to the logging destination and
stderr\&.
.PP
Before MySQL 5\&.1\&.20, error logging is controlled only with the
\fB\-\-log\-error\fR
option\&. If it is given, messages go to the named error file\&. Otherwise, messages go to the default error file\&.
.PP
Normally, you should not edit the
\fBmysqld_safe\fR
script\&. Instead, configure
...
...
@@ -689,7 +785,7 @@ option file\&. In rare cases, it might be necessary to edit
\fBmysqld_safe\fR
to get it to start the server properly\&. However, if you do this, your modified version of
\fBmysqld_safe\fR
might be overwritten if you upgrade MySQL in the future, so you should make a copy of your edited version that you can reinstall\&.
might be overwritten if you upgrade MariaDB in the future, so you should make a copy of your edited version that you can reinstall\&.
.PP
On NetWare,
\fBmysqld_safe\fR
...
...
@@ -727,7 +823,7 @@ tables\&.
.sp -1
.IP " 3." 4.2
.\}
Provides a screen presence for the MySQL server\&.
Provides a screen presence for the MariaDB server\&.