So far, the MySQL Server RPM packages as provided by MySQL AB used to automatically start the mysqld process after the package has been installed. It has been like that since the very beginning and we think of it as a convenience for our users when they want to get up and running quickly.

However, Kristian raised an interesting point in BUG#27072 where he points out that automatically starting mysqld during the RPM installation might not always be the desired behaviour, especially in automatic installation environments or during a fresh installation (where the system might not be fully configured yet). Therefore he proposes to change this behaviour to not start mysqld as part of the installation.

While I personally agree with his proposal,

  [Read more...]

Yesterday I received a sample copy of the "SUSE Linux 10.1 OSS - vorkon" DVD, which was assembled by Nicolaus Millin. While I have not installed it yet (as I by now have a very well running installation of SUSE Linux 10.1 on my laptop), the content of the DVD sounds very promising. In addition to incorporating all the updates that have been published since SUSE Linux 10.1 was released (around 100), this version also includes additional drivers like the 3D graphics drivers from ATI and nVidia, network card drivers like ndiswrapper, madwifi and rt2500 as well as drivers for AVM products and Logitech QuickCams. So the base system  [Read more...]

The release of MySQL 5.0 introduced the MySQL Instance Manager (IM), which intends to replace the mysqld_safe wrapper script as well as the mysqld_multi script that keeps track of multiple MySQL instances running on the same machine.

This article will qive you a quick overview about the IM and how to enable and configure a minimal setup that uses the IM to manage the default mysqld instance. I used MySQL 5.1.7-beta for my tests, some of this may work differently on other versions of MySQL.

Continue reading "Enabling and using the MySQL Instance Manager (IM)"