Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.1.16
-
None
-
None
Description
$ ./bin/mysqld --no-defaults --log-error --key-buffer=50M
|
2016-08-22 21:03:20 139855997585344 [Note] Using unique option prefix 'key-buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
|
2016-08-22 21:03:20 139855997585344 [Note] ./bin/mysqld (mysqld 10.1.17-MariaDB-debug) starting as process 28295 ...
|
Attachments
Issue Links
- relates to
-
MDEV-6873 On startup please make MariaDB report it's version number
-
- Closed
-
-
MDEV-9593 Print the real version in the error log
-
- Closed
-
-
MDEV-10967 Print the real version in the error log #2
-
- Closed
-
-
MDEV-17093 Print version_source_revision in the error log upon server startup
-
- Closed
-
-
MDEV-20287 Have the server process print a "starting mysql" message before first actual log message
-
- Closed
-
-
MDEV-20344 startup messages belong in stderr/error-log not stdout
-
- Closed
-
-
MDEV-21711 Log: "Server Version xx.xx.xx starting" as very first thing when an instance is starting
-
- Open
-
-
MDEV-21046 Print server version to error log instead of stderr during startup process
-
- Open
-
Maybe that's because the warning is produced before the log can be initialized? I remember it being the case for some warnings/errors before.