MySQL Bugs: #6621: Configuration Wizard doesn't populate [client] section of my.ini

Bug #6621	Configuration Wizard doesn't populate [client] section of my.ini
Submitted:	15 Nov 2004 6:42	Modified:	31 Mar 2014 10:18
Reporter:	Tom Metro	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Config Wizard	Severity:	S3 (Non-critical)
Version:	4.1.7, 5.0.79	OS:	Windows (Windows NT)
Assigned to:		CPU Architecture:	Any

Description:
The MySQL Server Instance Configuration Wizard on Windows does not populate the [client] section of the my.ini file it generates.

Also, it does not update the my.ini file located in the Windows directory that will be used by clients. (See related bug #2941, which was closed as "Not a Bug", but in my opinion it is a bug.)

I ran into this when I told the Wizard to configure the server instance to use only a named pipe. I then had to figure out the appropriate way to configure clients to use a named pipe. (Which required some experimentation, due to some weaknesses in the documentation. See bug #6620.)

How to repeat:
Run Server Instance Configuration Wizard.
Select option to use only a named pipe.
Observe that generated my.ini does not have a [client] section configured for a named pipe.
Observe that my.ini in Windows directory does not have a [client] section configured for a named pipe.

Thank you for the bug report.

Thanks for reporting. The problem in this case is, that the wizard cannot deal with complex configuration file setups. As the wizard only (re-)generates a fixed configuration file based on a template it does not touch a config file that might be shared by several MySQL installations but generates it's own config file in the installation directory.

This works well for the server, because the windows service is installed to read the generated configuration file. It also works for the command line client shortcut in the Windows Start Menu since the config file is specified there as well.

Now the problem is, if another client is started from the command line it will not find the configuration file, because it is one directory below and not in a "default" place (C:\ or C:\Windows).

We hope to address this in a future version of the client tools, so they automatically look up one directory to see if a configuration file is there.

Client section in generated my.ini is populated already:

[client]

port=3308

But there is still no option to change any default/existing my.ini outside of the installation directory.

Posted by developer:
 
Thank you for the bug report. We are closing this report now for two related reasons:

* MySQL Server 4.1 and 5.0 are obsolete versions of MySQL Server
* For more recent MySQL Server versions, the config wizard is no longer available, and the MySQL Installer for Windows is the recommended way to install MySQL Server on Windows

Close as per comment above.