This portal is to open public enhancement requests against IBM System Storage products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
Do you have any suggestions how we can do a recursive ACL change efficiently using mmputacl? For directory trees that include millions of files, running mmputacl on each file or directory using a file list generated by, let's say, the find command, can take huge amounts of time. Each acl change requires forking a process to mmputacl. Then, mmputacl requires an acl input file that it needs to read to set the acls. This is highly inefficient. mmputacl could benefit from a recursive option that can use PIT to quickly and efficiently traverse the directory hierarchy. I envision an mmputacl command with the following CLI:
mmputacl [-r --diracl aclfile --fileacl aclfile] | [[-d] [-i InFilename]] Filename
The -r option would indicate recursive acl change. It would require an acl file for plain files and another for directories. If the -r option is not given, then the command behaves as it does today.
Thank you.
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
This recursive option would be so helpful.. Especially with tools that create dirs ans subdirs while running for later sharing.
We definitely need a more efficient recursive option.
At this point, without a built-in recursive option, ACL updates can be painfully slow. To wit, one of the "recent" updates on a large, directory-ladened filesets has been chugging along for some two weeks and is still not complete.