Bug 1240506 - [Backup]: Required - man page for Glusterfind - glusterfs incremental API
Summary: [Backup]: Required - man page for Glusterfind - glusterfs incremental API
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterfind
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Bug Updates Notification Mailing List
QA Contact: Sweta Anandpara
URL:
Whiteboard:
Depends On:
Blocks: 1223636
TreeView+ depends on / blocked
 
Reported: 2015-07-07 06:59 UTC by Sweta Anandpara
Modified: 2018-04-16 03:03 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-16 03:03:45 UTC
Embargoed:


Attachments (Terms of Use)

Description Sweta Anandpara 2015-07-07 06:59:59 UTC
Description of problem:

Glusterfind being a new feature, it is required to have a man/info page to let users know what the API is all about.

Man/info when done on glusterfind currently displays 'No manual entry for glusterfind' OR 'no menu item glusterfind in node'


Version-Release number of selected component (if applicable):
glusterfs-3.7.1-7.el6rhs.x86_64

How Reproducible: Always

Additional info:

[root@dhcp43-93 ~]# man glusterfind
No manual entry for glusterfind
[root@dhcp43-93 ~]# glusterfind 
usage: glusterfind [-h] {pre,create,list,post,delete} ...
glusterfind: error: too few arguments
[root@dhcp43-93 ~]#
[root@dhcp43-93 ~]# info glusterfind
...
...
* __fwritable: (libc)Opening Streams.
-----Info: (dir)Top, 1977 lines --Top---------------------------------------------------------------------------------------------------------------------------------------------------------
No menu item `glusterfind' in node `(dir)Top'.

Comment 2 Sweta Anandpara 2015-07-09 05:59:25 UTC
Proposing it as a blocker as it won't be good to release this utility hook without its corresponding man page.

Comment 4 Amar Tumballi 2018-04-16 03:03:45 UTC
Feel free to open this bug if the issue still persists and you require a fix. Closing this as WONTFIX as we are not working on this bug, and treating it as a 'TIMEOUT'.


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