MySQL Bugs: #60216: bind-address unknown in 5.5.9 client

Bug #60216	bind-address unknown in 5.5.9 client
Submitted:	23 Feb 2011 7:49	Modified:	28 Feb 2011 11:22
Reporter:	Karl Blessing	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S2 (Serious)
Version:	5.5.8, 5.5.9	OS:	Any (FreeBSD, Windows XP)
Assigned to:	Jon Stephens	CPU Architecture:	Any
Tags:	5.5.9, address, BIND, client, MySQL

Description:
I'm using the MySQL Client 5.5.9 (installed from FreeBSD ports), and I cannot use --bind-address nor bind-address in a my.cnf.

I receive an error:
mysql: unknown variable 'bind-address=10.0.0.2'

for both instance, even though the documentation here says the feature has been available since 5.5.8

How to repeat:
Simply use --bind-address in command line, or bind-address in my.cnf for mysql client 5.5.9 on FreeBSD

Indeed, this does not work:

C:\Program Files\MySQL\MySQL Server 5.5\bin>mysql --version
mysql  Ver 14.14 Distrib 5.5.8, for Win32 (x86)

C:\Program Files\MySQL\MySQL Server 5.5\bin>mysql --bind-address=127.0.0.1 -uroo
t -proot -P3312 test
mysql: unknown variable 'bind-address=127.0.0.1'

Neither with 5.5.8, nor with 5.5.9, even on Windows.

looks like bug #25939 fixes didn't go into 5.5 or 5.1.
however, mysql-trunk builds have --bind-address for clients.  
maybe this is just a docs bug?

http://dev.mysql.com/doc/refman/5.5/en/mysqladmin.html#option_mysqladmin_bind-address

http://dev.mysql.com/doc/refman/5.5/en/mysql-command-options.html#option_mysql_bind-addres...

Hopefully not just a docs bug, it would be nice to actually have bind-address ability for clients for security purposes.

MySQL Server 5.5 unfortunately does not have support for setting --bind-address in client.

It will be available in a future release of MySQL Server. 

Sorry about it showing up in the manual already.

Aww... Oh Well... closing bug report.

Bug shouldn't have been closed -- should be Verified as Docs bug.

Set P2/S2 (yes, this is a serious problem).

Assigning to myself for handling.

Sorry didn't realize there was specifically a Docs category.

Sorry did not realize there was specifically a docs category.

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.

This actually affects the 5.5 documentation for a number of MySQL client programs, not just the mysql client.

Further fix made here: http://lists.mysql.com/commits/132108