http://qa.mandrakesoft.com/show_bug.cgi?id=3208
------- Additional Comments From [EMAIL PROTECTED] 2003-03-12 07:56 ------- Created an attachment (id=335) --> (http://qa.mandrakesoft.com/attachment.cgi?id=335&action=view) makes it look also for mysqld-max, not only mysqld The patch fixes the reported problem for me. The check for mysqld-max is heavily based on the one in mysqld_safe in order to reduce the risk. I was careful to not brake anything and tested it with both packages MySQL-Max and MySQL for 4.0.11a-4mdk. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: This belongs to the MySQL-common package, but it was not in the selection list. Problem: mysql_install_db fails to look for mysqld-max and therefore does not initialize /var/lib/mysql/mysql properly. Sorry that I only noticed this so late, but since /var/lib/mysql is kept on uninstall, the problem only happens when you never installed MySQL before *and* install MySQL-Max before MySQL. It is a bug in the original script and not by Mandrake's package, but only became visible when MySQL-Max became undependend of MySQL package. And reporting it the ordinary way would propagate to late for the 9.1 release. I will attach a patch.
