Bug #23906 Using administrator to change startup variables cuases strange behavior
Submitted: 2 Nov 2006 19:54 Modified: 3 Nov 2006 13:36
Reporter: Kevin Roberts (Candidate Quality Contributor) Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Administrator Severity:S2 (Serious)
Version:1.2.5 rc OS:Windows (Windows Server 2003)
Assigned to: CPU Architecture:Any

[2 Nov 2006 19:54] Kevin Roberts 
Description:
Using Administrator to apply changes to the startup variables in my.ini causes numerous problems. Very unstable.

I had to return to using 1.2.4. 

How to repeat:
If you use administrator to use old passwords and save the changes, all the settings in my.ini get commented out. I think this is why the Administrator was able to stop the MySQL service, but could not restart it (had to restart it via the Windows "Services" window).

If you edit my.ini manually and remove the hash sigh from the start of the lines (i.e. uncomment it), the change is still not recognized in Administrator.

Example: having "old-passwords" on a line by itself in my.ini does not result in Administrator recognizing it and putting a check mark in the Old Passwords checkbox. Creating new user accounts result in new-style passwords getting created instead of old-style (as evidenced by the sisze of the encrypted password in the mysql.user table.

Note that when I went back to Administrator 1.2.4, the old-passwords directive still did not appear to work.
[3 Nov 2006 7:43] Sveta Smirnova 
Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Duplicates Bug #23885
[3 Nov 2006 7:44] Sveta Smirnova 
Please provide content of your configuration file too.
[3 Nov 2006 13:36] Kevin Roberts 
Sorry. I did try to see if the bug was already in the database prior to submitting my bug (I always do), but did not find it.