Bug 1388769 - RFE: open-vm-tools utilities should recognize -h option
Summary: RFE: open-vm-tools utilities should recognize -h option
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: open-vm-tools
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ravindra Kumar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-26 07:32 UTC by Marko Myllynen
Modified: 2018-11-27 18:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-27 18:25:14 UTC
Type: Bug


Attachments (Terms of Use)

Description Marko Myllynen 2016-10-26 07:32:17 UTC
Description of problem:
vmware-rpctool / vmware-hgfsclient / vmware-xferlogs do not understand the more or less standard -h option to print out a help messages. It would be nice if -h (possibly also --help) would work with all the commands provided in the open-vm-tools package.

Comment 1 Ravindra Kumar 2016-10-26 18:12:52 UTC
I understand we don't have good documentation. However, we do print the command syntax, e.g.:

$ vmware-rpctool
rpctool syntax:

  rpctool <text>

$ vmware-xferlogs
xferlogs <options> <filename>
options - enc/dec

We do have plans to add man pages for all commands.

Comment 2 Marko Myllynen 2016-10-27 08:13:36 UTC
(In reply to Ravindra Kumar from comment #1)
> 
> We do have plans to add man pages for all commands.

Thanks, this sounds very good.

Comment 3 Fedora End Of Life 2017-11-16 19:20:05 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 4 Ben Cotton 2018-11-27 18:06:06 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ravindra Kumar 2018-11-27 18:24:19 UTC
This was fixed a while back upstream in version 10.2.0.

Comment 6 Ravindra Kumar 2018-11-27 18:25:14 UTC
Closing as it has been fixed a while ago in open-vm-tools version 10.2.0 and later.


Note You need to log in before you can comment on or make changes to this bug.