Description: If a "skip-show-database" argument is processed by mysqld *after* a "port=[number]" argument, mysqld will listen to port 3306 regardless.

It does not matter whether the arguments are specified in a my.[ini|cnf] file or on the command line (or one of each, with other arguments in between or not). If the command mysqld --print-defaults shows a "skip-show-database" directive after a "port=" directive, the latter directive will be ignored.

Specifying "skip-show-database" *before* "port=" has no ill effect.

EXAMPLES: mysqld --port=3399 --skip-show-database --standalone -> runs on port 3306 mysqld --skip-show-database --port=3399 --standalone -> runs on port 3399 mysqld --port=3399 --skip-show-database --port=3301 --standalone -> runs on port 3301

This behavior holds for all mysqld variants I tested: mysqld, mysqld-nt, mysqld-max-nt. Note: I downloaded the binary 3.23.52 distro from the MySQL AB web site. This took me *hours* to track down. It is a very subtle flaw.

How-To-Repeat: Specify a "skip-show-database" argument to mysqld *after* a "port=[number]" argument.

Fix: Specify a "skip-show-database" argument to mysqld *before* a "port=[number]" argument.

Synopsis: mysqld "skip-show-database" argument after "port=" argument nullifies the latter. Submitter-Id: Originator: Zach Pincus Organization: Stanford Program in Biomedical Informatics MySQL support: none Severity: non-critical Priority: medium (it's VERY non-obvious how to work around this!) Category: mysqld Class: sw-bug Release: mysql-3.23.52 Executable: mysqld, mysql-nt, mysqld-max-nt (others not tested) Environment: Gateway PIII model GP7-500, 384 MB RAM. System: NT 4.0 SP6a Compiler: I downloaded a binary distro. Architecture: i386