summaryrefslogtreecommitdiffstats
path: root/libglusterfs
diff options
context:
space:
mode:
authorkshithijiyer <kshithij.ki@gmail.com>2019-06-28 15:32:31 +0530
committergluster-ant <bugzilla-bot@gluster.org>2019-06-28 15:32:31 +0530
commit1b2b4ca4023874b95d37e99dbc51c443d4f76f70 (patch)
treea9ce595f402cde8060605eb57198f4921224fc67 /libglusterfs
parent887f03e46aff909c493a4447eaed4feb89f6a47f (diff)
downloadglusterfs-1b2b4ca4023874b95d37e99dbc51c443d4f76f70.tar.gz
glusterfs-1b2b4ca4023874b95d37e99dbc51c443d4f76f70.tar.xz
glusterfs-1b2b4ca4023874b95d37e99dbc51c443d4f76f70.zip
Removing one top command from gluster v help
The current help show 2 different top commands intead of one single top command which can be easily observed when "# gluster v help" command is issued. Removing one "volume top <VOLNAME>" and clubbing into them into a single command. Current help: volume top <VOLNAME> {open|read|write|opendir|readdir|clear} [nfs|brick <brick>] [list-cnt <value>] | volume top <VOLNAME> {read-perf|write-perf} [bs <size> count <count>] [brick <brick>] [list-cnt <value>] - volume top operations Expected help: volume top <VOLNAME> {open|read|write|opendir|readdir|clear} [nfs|brick <brick>] [list-cnt <value>] | {read-perf|write-perf} [bs <size> count <count>] [brick <brick>] [list-cnt <value>] - volume top operations fixes: bz#1725034 Change-Id: Ifbc4c95f2558286e27dfc5e9667046b80eb1715d Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
Diffstat (limited to 'libglusterfs')
0 files changed, 0 insertions, 0 deletions