| Bug #854 | ambiguity surrounds mysqld-max | ||
|---|---|---|---|
| Submitted: | 16 Jul 2003 10:58 | Modified: | 18 Jul 2003 13:23 |
| Reporter: | xian | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
| Version: | 4.0.13-0 | OS: | Linux (RHL9) |
| Assigned to: | Paul DuBois | CPU Architecture: | Any |
[16 Jul 2003 11:17]
Paul DuBois
I do not understand the nature off the ambiguity that you are referring to. In the first couple of paragraphs, you're comparing Windows and Unix servers, which are not always equivalent. In the next couple of paragraphs, you refer to RPM files distributed by Red Hat. But these are not necessarily the same as those distributed by MySQL AB. We have no control over what Red Hat distributes.
[16 Jul 2003 11:32]
Paul DuBois
If you wish to clarify this report, please add another comment. Thanks.
[16 Jul 2003 12:14]
xian
Let's talk unix. Particularly, there is no mysql-max in the "official" list of rpms, found here: http://www.mysql.com/doc/en/Linux-RPM.html while there is a single (erroneous?) mention to one here: http://www.mysql.com/doc/en/mysqld-max.html "The mysqld-max RPM uses the above mentioned mysqld_safe feature. It just installs the mysqld-max executable and mysqld_safe will automatically use this executable when mysqld_safe is restarted. " This alone calls into question whether or not mysql AB distributes a mysql-max rpm, and if not, which rpms listed in Linux-RPM.html are necessary/sufficient for InnoDB support. To complicate things further, a rpmfind.net search reveals mysqld-max packages where "Vendor=Mysql AB". As such, I might assume they have been released by Mysql AB, whereas looking at Linux-RPM.html leads me to believe they have not been released by Mysql AB. Sorry about the redhat static. They do weird stuff, and I'm having a hard time figuring out what they're doing, not quite seeing myself what the "right and proper" way is. Thanks much, xian
[18 Jul 2003 13:23]
Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant product(s). Thanks for pointing out the problem.
Description: In the manual at page: http://www.mysql.com/doc/en/InnoDB_start.html the file mysqld-max is discussed: "For example, in Windows you can start `mysqld-max.exe' with: your-path-to-mysqld\mysqld-max --console However, I am able to run this command: mysql> /usr/sbin/mysqld --console and, with my system properly configured, have the InnoDB engine run properly. Overall, there is ambiguity in this document regarding a MySQL-max RPM. Particularly, an RPM is explicitly mentioned here: http://www.mysql.com/doc/en/mysqld-max.html but not here: http://www.mysql.com/doc/en/Linux-RPM.html ASFIsee, Red Hat Linux does *not* distribute this RPM, but rather includes it in the standard (or devel?) distribution. How to repeat: rpmfind.net turns up 30 packages for mysql-max, 20 of them with Distribution=mysql, none from RHLinux. I am able to run InnoDB and I have installed the following packages, all from RHLinux9 mirrors, host>rpm -q -a | grep -i mysql MySQL-client-4.0.13-0 MySQL-server-4.0.13-0 MySQL-devel-4.0.13-0 MySQL-shared-4.0.13-0 MySQL-shared-compat-4.0.13-0 perl-DBD-MySQL-2.1021-3 Suggested fix: Provide explanation/rationale in http://www.mysql.com/doc/en/InnoDB_start.html. Correct inconsistency between http://www.mysql.com/doc/en/mysqld-max.html http://www.mysql.com/doc/en/Linux-RPM.html