| Bug #54961 | storage engine plugins do not work with mysqld_safe in 5.5.4-m3 in sandbox | ||
|---|---|---|---|
| Submitted: | 2 Jul 2010 14:56 | Modified: | 5 Jul 2010 6:17 |
| Reporter: | Zardosht Kasheff (OCA) | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server: Packaging | Severity: | S3 (Non-critical) |
| Version: | 5.5 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | Contribution | ||
[5 Jul 2010 6:17]
Sveta Smirnova
Thank you for the report. This is duplicate of bug #52737

Description: can not run 5.5.4-m3 in a mysql sandbox. the cause is the plugin-dir change to the mysqld_safe script. we would like these rules to apply: * the plugin directory has precedence over the base directory * the base directory has precedence over the default base directory this change implements these rules: =================================================================== --- mysqld_safe.sh (revision 19809) +++ mysqld_safe.sh (working copy) @@ -702,7 +702,7 @@ cmd="`mysqld_ld_preload_text`$NOHUP_NICENESS" -plugin_dir="${PLUGIN_DIR:-@pkgplugindir@}${PLUGIN_VARIANT}" +plugin_dir="${PLUGIN_DIR:-${MY_BASEDIR_VERSION}/lib/mysql/plugin}${PLUGIN_VARIANT}" for i in "$ledir/$MYSQLD" "$defaults" "--basedir=$MY_BASEDIR_VERSION" \ "--datadir=$DATADIR" "--plugin-dir=$plugin_dir" "$USER_OPTION" How to repeat: see above Suggested fix: see above