Bug #51802 Incorrect detection of the mysql startup script on Fedora
Submitted: 7 Mar 2010 7:06 Modified: 10 Mar 2010 16:27
Reporter: Georgiy Okrokvertskhov Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S3 (Non-critical)
Version:5.2.16 OS:Linux (Fedora 12)
Assigned to: Johannes Taxacher CPU Architecture:Any
Tags: script, start, stop, workbench

[7 Mar 2010 7:06] Georgiy Okrokvertskhov
Description:
New server instance wizard can't find correct start-up script for the MySQL instance on Fedora 12.

How to repeat:
1. Go to New server instance
2. Click next (will create instance for localhost)
3. Provide user name and password
4. Click next
5. Set MySQL installation type Fedora Linux (Vendor Package)
6. Click next

Result:
testing Host Machine settings failed to find mysql startup script
Operation failed: /etc/init.d/mysql start is invalid

But on the next page Section of the Server instance shows correct name 'mysqld'
Check name and Check Path show valid results

If you click next and go to next page start and stop commands use again 'mysql' name instead of 'mysqld'
[9 Mar 2010 2:36] MySQL Verification Team
Thank you for the bug report.
[9 Mar 2010 10:14] Johannes Taxacher
theres no actual "detection" going on trying to find the script. Workbench takes the default information for a specific system from the profile-templates provided.
fedora templates have been changed to use mysqld as start-/stop-script name.
fixed in reporitory
[10 Mar 2010 16:27] Tony Bedford
A entry has been added to the 5.2.17 changelog:

The New Server Instance wizard did not set the correct name for the startup script, when the installation type was set to Fedora Linux (Vendor Package). Testing the connection resulted in the error “Operation failed: /etc/init.d/mysql start is invalid”.