Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.4(EOL), 10.5, 10.6, 10.11, 11.0(EOL), 11.1(EOL), 11.2(EOL), 11.3(EOL)
-
linux
Description
The command
mysqlbinlog -R --socket=/var/lib/mysql/mysql.sock --stop-never
|
simply does not show any errors, it just outputs the help page and configuration. If there is anything missing, or incorrect, the command should return an error message.
Attachments
Activity
Sorry, it looked to me, if specifying the remote options, the file name is optional, as mysqlbinlog would handle the filename itself.
I guess it is always a good thing, to return the cause of the error instead of just showing the possible options.
Right. mysqlbinlog must be invoked as
Usage: mysqlbinlog [options] log-filesthat is a log file name is not optional. If it's not specified, mysqlbinlog prints the usage message, although it would've been more user friendly to say something like "binog file name is not specified"