MySQL Bugs: #14319: mysqld_safe ignore err-log parameter from my.cnf

Bug #14319	mysqld_safe ignore err-log parameter from my.cnf
Submitted:	26 Oct 2005 8:44	Modified:	26 Oct 2005 9:59
Reporter:	Andrew Sitnikov	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	5.0.15	OS:	Linux (Suse 10.0)
Assigned to:		CPU Architecture:	Any

Description:
After upgrading from Version 4.1 to 5.0 mysqld_safe ignore err-log parameters in  /etc/my.cnf and create default err log file in datadir.

How to repeat:
upgrade 4.1 to 5.0

Suggested fix:
Add --log-error param wnen run mysqld_safe

According to the manual (http://dev.mysql.com/doc/refman/5.0/en/error-log.html):

"You can specify where mysqld stores the error log file with the --log-error[=file_name]  option. If no file_name value is given, mysqld uses the name host_name.err  and writes the file in the data directory."

So, in version 5 you have to set option log-error for mysqld to change the default location. Look:

[openxs@Fedora 5.0]$ cat /tmp/mysql.err
051026 12:44:25  mysqld started
051026 12:44:25  InnoDB: Started; log sequence number 0 26133837
051026 12:44:25 [Note] /home/openxs/dbs/5.0/libexec/mysqld: ready for connections.
Version: '5.0.16'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
[openxs@Fedora 5.0]$ cat my.cnf
[mysqld]
log-error=/tmp/mysql.err
#err-log=/tmp/mysql.err

So, this is how I had just started by 5.0.16-BK. err-log option did not worked in [mysqld_safe] section and was reported as:

051026 12:42:51  mysqld started
051026 12:42:51 [ERROR] /home/openxs/dbs/5.0/libexec/mysqld: unknown variable 'err-log=/tmp/mysql.err'

when set in [mysqld] section. So, I do not think it is a bug. Just a small change in behaviour, even documented.

i can not find any mentions about that:
http://dev.mysql.com/doc/refman/5.0/en/upgrading-from-4-1.html

my viewpoint is since mysql4.1 use err-log param from my.cnf and 5.0 not use, this must be documented is this article