Bug #29450 mysqld_safe tries to touch / chown empty $log_err file
Submitted: 29 Jun 2007 18:36 Modified: 17 Jul 2007 17:28
Reporter: Timothy Smith Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Command-line Clients Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: Assigned Account CPU Architecture:Any

[29 Jun 2007 18:36] Timothy Smith 
Description:
Changes for bug #4858 make it possible for $log_err to be empty; however, mysqld_safe still tries to touch & chown $log_err, which causes warnings to be emitted.  The warnings are harmless, but mysqld_safe should just skip those commands.

How to repeat:
Ensure that your my.cnf doesn't include a --log-error setting, and run mysqld_safe.  Look for warning output from 'touch' and 'chown':

With sh -x, it looks like:

...
+ USER_OPTION=--user=mysql
+ touch
usage: touch [-acfm] [-r file] [-t [[CC]YY]MMDDhhmm[.SS]] file ...
+ chown mysql
usage: chown [-fhv] [-R [-H | -L | -P]] owner[:group] file ...
       chown [-fhv] [-R [-H | -L | -P]] :group file ...
+ test -n ''
...
[17 Jul 2007 17:28] Timothy Smith 
Duplicate of bug #29634