Bug #5636 Named pipes option setting in Administrator is inconsistent with my.cnf file
Submitted: 18 Sep 2004 1:17 Modified: 20 Sep 2004 12:43
Reporter: Shuichi Tamagawa Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Administrator Severity:S2 (Serious)
Version:1.0.12-GA OS:Windows (Win XP / SP2)
Assigned to: CPU Architecture:Any

[18 Sep 2004 1:17] Shuichi Tamagawa
Description:
Named pipes option setting in MySQL Query Browser is inconsistent with my.cnf.
As a result it is possible that mysql server doesn't start.

How to repeat:
Add "enable-named-pipe" option to the [mysqld] of my.cnf file.
In the Query Browser go to 'Service Control' -> 'Configure Service' tab.
Uncheck the 'Named Pipes' option check box.
Click 'Apply Changes'.
Check the my.cnf file('enable-named-pipe' option is still active).
Restart mysql service -> 'System Error' 

Suggested fix:
It should be consistent.
[18 Sep 2004 8:59] Shuichi Tamagawa
Correction. This is about MySQL Administrator.
[20 Sep 2004 12:43] Michael G. Zinner
It is true that MySQL Administrator should prevent people to generate an invalid system configuration. But it is not possible to filter out all invalid settings. 

Therefore, we added a new Server Instance Configuration Wizard to the 4.1 server setup. It allows an easy configuration of the server that will always work.

If someone is using MySQL Administrator to edit the .cnf file manually it is expected that one is knowing what he/she is doing. It is like a Windows user using the RegEdit to modify registry settings... it is never trivial.
[20 Sep 2004 19:41] Shuichi Tamagawa
So what is the "Named Pipes" check box for?