MySQL Bugs: #2941: new installation still use old configuration file

Bug #2941	new installation still use old configuration file
Submitted:	24 Feb 2004 12:03	Modified:	4 Mar 2004 5:41
Reporter:	li luo	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S3 (Non-critical)
Version:	4.1.1a-alpha	OS:	Windows (windows 2000 pro)
Assigned to:		CPU Architecture:	Any

Description:
When you uninstall an old version of mysql, my.ini, normally in 
Windows/WINNT directory, is not deleted or reset. When you install 
a new version, the new version will still use the old my.ini file. 
Most of the time, the configuration is still valid and desirable. 
However, if you install the new verion is a different directory, 
every thing mess up cause the cause the "basedir" option in the 
old ini file points to the wrong location: when you start mysqld 
from windows service manager, you just get an error message 
"Error 1067: the process terminited unexpectly". Even if you start 
mysqld from command line, there is no message to specify the directory 
problem.

How to repeat:
uninstall current version of mysql
install new version in a different directory
mysqld won't start cause it still reads the old my.ini file pointing to wrong directory.

Suggested fix:
At least mysqld should give user a message when it find out that 
the directory of current mysqld instance is different than the one 
specified in my.ini file, such as "basedir is different from where 
current mysqld instance located..."

What happens is that the currently installer doesn't remove
the my.ini during the un-install process and don't creates
a new one during the new install.

Sorry but that should be made manually currently.

A new installer is in the work.

Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.mysql.com/documentation/ and the instructions on
how to report a bug at http://bugs.mysql.com/how-to-report.php