Bug #6696 ndb_mgm command line options inconsistent with behaviour

Submitted:	18 Nov 2004 13:27	Modified:	18 Nov 2004 17:40
Reporter:	Arjen Lentz	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	4.1.7	OS:	Linux (linux)
Assigned to:	Tomas Ulin	CPU Architecture:	Any

Description:
# ndb_mgm --help
Usage: ndb_mgm [--try-reconnect=#] [-t #] [--usage] [-?] [host [port]]

Shown here is that specifying the port number is optional.

# ndb_mgm 192.168.50.36
-- NDB Cluster -- Management Client --
Connecting to Management Server: 192.168.50.36:0
NDB> 

But here it shows port 0.
So there should either be a default, or specifying the port number should be mandatory.

How to repeat:
See above.

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Page generated in 0.048 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.