Bug #17861 MySQL-Max binary is preferred by the startup script
Submitted: 2 Mar 2006 14:26 Modified: 6 Apr 2006 13:37
Reporter: Lenz Grimmer Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Packaging Severity:S2 (Serious)
Version:5.1.7 OS:Linux (Linux)
Assigned to: Kent Boortz CPU Architecture:Any

[2 Mar 2006 14:26] Lenz Grimmer
The 5.1.7 MySQL-server RPM now contains both a mysqld and mysqld-max binary. This means that the mysqld-max binary will be started by default, as the startup script mysqld_safe prefers it over a plain mysqld binary.

How to repeat:
Install 5.1.7 from RPM, start up the server and observe it's using the mysqld-max binary.

Suggested fix:
Please remove the check for mysqld-max in mysqld_safe or consider changing the mysql.server init script to use the instance manager by default (see BUG#17440 for my proposal to change this for 5.1)
[2 Mar 2006 21:54] 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:

[13 Mar 2006 18:41] Mike Hillyer
What version does the patch apply to?
[31 Mar 2006 11:27] Kent Boortz
This will be in 5.1.9 beta
[6 Apr 2006 13:37] Jon Stephens
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at

Additional info:

Documented feature change in 5.1.9 changelog. Closed.