MySQL Environment MyEnv 1.0.1 has been released

Tue, 2013-11-05 16:03 — sales_en

FromDual has the pleasure to announce the release of the new version 1.0.1 of its popular multi-instance MySQL Environment MyEnv.

You can download MyEnv from here.

In the inconceivable case that you find a bug in MyEnv please report it to our Bugtracker.

Any feedback, statements and testimonials are welcome as well! Please send them to feedback@fromdual.com.

If you have questions about MyEnv we will answer them in the MyEnv forum.

Upgrade from 1.0 or 1.0.x to 1.0.y

# cd /home/mysql/product
# tar xf /tmp/myenv-1.0.y.tar.gz
# rm -f myenv
# ln -s myenv-1.0.y myenv

New alias v introduce for echo $MYENV_VERSION.
Function start was extended by --option. This allows you to start a Galera cluster node as follows: start --wsrep-cluster-address="gcomm://" (Bug #58).
Requirements for Ubuntu in README added.
Mismatch between my.cnf and myenv.conf or [mysqld] section and [client] section in my.cnf is checked and reported (Bug #71).
Before an instance is started MyEnv will check if file mysql/user.frm is created just in case installation was missing (Bug #82).
Non default PID file name is handled properly (Bug #64).
Starting an instance will also report SUCCESS or ERROR.
Instance check mysqladmin ping was improved by adding a timeout (Bug #56).
User to start MySQL instance is checked (Bug #69).
The scripts start and stop are much more robust (Bug #66).
Internal sequence of checks during start and stop has been changed.
Package recommendation for SLES/OpenSuSE completed.
Fixes around the POSIX functions for SLES/OpenSuSE.
Fake around missing signal constants for SLES/OpenSuSE and more verbose error messages.
Check for missing POSIX features added (Bug #59).
MyEnv start-up and check sequence changed.

Deleting a non existing instance is handled properly.
Empty basedir is handled properly.
Installation on /etc/my.cnf is handled properly (Bug #62).
Installation of my.cnf is redesigned, prepared for future features and error handling is improved.
mysql_install_db is also searched in bin path for NDB (MySQL Cluster) set-ups.
Installer is checking at the right location to decide if an instance is already installed or not (#Bug #83).
Installer should not be started as root user. Throwing warning (Bug #61).
Installer has additional suggestion for socket name: mysql-instance.sock, whole installation process is broken up in more pieces for future improvements, test cases were added (Bug #60).
Delete instance error messages made more clear (Bug #89).