MySQL Bugs: #49577: Manage server instance should have more appropriate behavior

Bug #49577	Manage server instance should have more appropriate behavior
Submitted:	10 Dec 2009 9:30	Modified:	25 Jun 2013 17:19
Reporter:	Nidhi Shrotriya	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.2.10	OS:	Linux (ubuntu 9.04)
Assigned to:		CPU Architecture:	Any

Description:
Manage server instances -> server1 -> connection1 (using Local Socket/Pipe option socket=/tmp/mysql.sock, user=root, password ='nidhi')

Server Administration-> choose 'server1' -> ok -> gets error as could not connect to server at None@None can't connect to local server through socket -> click continue anyway -> startup tab -> click start server -> asks for super user password -> given -> ok -> can't start server 

It is because it is always using /etc/my.cnf specified in System Profile of Manage server instance. But how would user get to know he had to update System Profile. 

Instead of System Profile tab it should be 'next' button giving both options -> using .cnf file or --no-defaults (with basedir/datadir) and then only should be able to finish the process, so that user knows it completed what all is required.

How to repeat:
As mentioned in description.

Thank you for the bug report.

This is maximum a feature request.

Server is looking for my.cnf by automatism always in installation path, home, /etc and /etc/mysql

You can configure where to find my.cnf in instance.

Also you can configure that server should start with --defaults-file=PATH/my.cnf

Additionally, you could write it into your init.d script.

We will discuss if we want to change behaviour here.

Closing as this was fixed a long time ago.