Bug #19298 mysqld_safe still uses obsolete --skip-locking parameter
Submitted: 24 Apr 2006 14:34 Modified: 7 Jul 2006 2:03
Reporter: Oli Sennhauser Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.1-5.1 OS:Any (all)
Assigned to: Iggy Galarza CPU Architecture:Any

[24 Apr 2006 14:34] Oli Sennhauser
Description:
mysql_safe still uses obsolete --skip-locking parameter

How to repeat:
grep skip safe_mysqld
$NOHUP_NICENESS $ledir/$MYSQLD $defaults --basedir=$MY_BASEDIR_VERSION --datadir=$DATADIR $USER_OPTION --pid-file=$pid_file --skip-locking >> $err_log 2>&1
eval "$NOHUP_NICENESS $ledir/$MYSQLD $defaults --basedir=$MY_BASEDIR_VERSION --datadir=$DATADIR $USER_OPTION --pid-file=$pid_file --skip-locking $args >> $err_log 2>&1"

Suggested fix:
use --skip-external-locking instead.
[24 Apr 2006 14:52] MySQL Verification Team
Thank you for the bug report.
[27 Jun 2006 5:35] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/8286
[27 Jun 2006 22:06] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/8355
[7 Jul 2006 2:03] Paul DuBois
Not a user-visible change.
No changelog entry needed.