Update documentation

This commit is contained in:
Johan Wikman
2017-05-18 10:56:34 +03:00
parent 8a2112cce6
commit ed97b4b22c
18 changed files with 37 additions and 37 deletions

View File

@ -677,7 +677,7 @@ MaxScale>
# Working With Servers
The server represents each of the instances of MySQL or MariaDB that a service
The server represents each of the instances of MariaDB or MySQL that a service
may use.
## What Servers Are Configured?
@ -1197,7 +1197,7 @@ MySQLAuth | Authenticator | V1.1.0 | 1.1.0 | GA
MySQLClient | Protocol | V1.1.0 | 1.1.0 | GA
MaxAdminAuth | Authenticator | V2.1.0 | 1.1.0 | GA
maxscaled | Protocol | V2.0.0 | 1.1.0 | GA
MySQLBackendAuth | Authenticator | V1.0.0 | 1.1.0 | GA
MySQLBackendAuth| Authenticator | V1.0.0 | 1.1.0 | GA
MySQLBackend | Protocol | V2.0.0 | 1.1.0 | GA
mysqlmon | Monitor | V1.5.0 | 3.0.0 | GA
schemarouter | Router | V1.0.0 | 2.0.0 | Beta

View File

@ -1,10 +1,10 @@
# Maxbinlogcheck, the MySQL/MariaDB binlog check utility
# Maxbinlogcheck, the MariaDB binlog check utility
# Overview
Maxbinlogcheck is a command line utility for checking binlogfiles. The files may
have been downloaded by the MariaDB MaxScale binlog router or they may be
MySQL/MariaDB binlog files stored in a database server acting as a master in a
MariaDB binlog files stored in a database server acting as a master in a
replication environment. Maxbinlogcheck checks the binlog files against any
corruption and stored incomplete transactions and reports a transaction summary
after reading all the events. It may optionally truncate the binlog file.