MySQL Bugs: #2833: Changing config file requires Administrator restart to function.

Bug #2833	Changing config file requires Administrator restart to function.
Submitted:	16 Feb 2004 17:20	Modified:	21 Jun 2004 14:17
Reporter:	Jacob Floyd	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.0.1a-alpha	OS:	Microsoft Windows (Win2k Advanced Server)
Assigned to:	Michael G. Zinner	CPU Architecture:	Any

Description:
If you change the config file (ie my.ini or my.cnf, etc) to a different file, or move the file to another directory (ie C:/MySQL to C:/WINNT), and then try to change a startup configuration, it gives an error that the file is being used by another process and states the name of the old file.

How to repeat:
1) Change the config file to a different file.
2) Go to the startup configuration stuff in Administrator.
3) Change something.
4) Click Apply Changes.
5) An error should occur stating that such and such a file (the old one) is being used by another process.

Another method for recreating this error:
1) Open Administrator
2) Open your configuration file in a text editor like WordPad or NotePad.
3) Change some startup configuration in Administrator
4) Click Apply Changes.
5) The Error.

Unable to give exact wording of error at this time due to a terminal-services time -out in effect on the server. Will post later (if I remember)

Suggested fix:
A workaround until a new version fixes this is to simply restart administrator before trying to change the startup configuration.

A good thing to do in a future version would be to have the program reload the configuration file when you click apply settings on the page that the file was changed. This would ensure that it is trying to use the correct configuration file.
Another option for a future release is to have a button or option that refreshes the configuration file.

OK,
I got access to a copy (It's not local) so I can tell you what things happened (sort of)
Here some stuff in more detail:

How to repeat:
Case 1:
In the Service Control Section
Under the Configure Service Tab
1) Change the 'Configuration Filename' to a different file.
2) Go to the 'Startup Variables' stuff in Administrator.
3) Change something.
4) Click Apply Changes.
5) An error should occur stating that such and such a file (the old one) is
being used by another process.

Another method for recreating this error:
1) Open Administrator
2) Open your configuration file in a text editor like WordPad or NotePad.
3) Change some 'Startup Variable' in Administrator
4) Click Apply Changes.
5) The Error.

Still unable to say what the error is because "This section is only available when connected to local host".

Sorry, after I restart the server on site I will see if I can get that error.
Thanks,
Jacob

OK, here we go, more info on the bug.
(Sorry for taking so long to describe it accuratly, if there was a way to edit what I originally sent, then I might be able to do better at keeping it short. Just an idea)

I can't seem to get it to repeat the error message. My guess is that I was doing something wrong. However, If you change the configuration file (leaving the old one intact in the same spot with the same name) to a different file (e.g. you switch from a file called 'C:/WINNT/my.ini' to 'C:/WINNT/my.cnf' using administrator, and (following clicking the 'apply changes' button) you change some setting like, say the temporary directory, then it will change the info in the ORIGINAL file (the my.ini file) and NOT the file you switched it to (my.cnf in my case).

I think this is the best explanation so far. If I have a chance, I'll download the code and see if I can suggest how to change it to fix this particular bug, but don't count on me, I'm pressed for my time.

Thanks,
Jacob

Could you tell what you mean by "switching" the option file?

You mean moving the file with the Windows Explorer? MySQL Administrator cannot detect that. It always uses the file c:\my.cnf or c:\windowsdir\my.ini or the file specified when installing MySQL as a service.

But we have improved the option file handling a lot in 1.0.2a. Please take a look if the error is still present!

Thanks!