On 9/7/05, Shailabh Nagar <[EMAIL PROTECTED]> wrote: > Paul Menage wrote: > > Hi, > > > > Has anyone considered using CKRM to implement a "directory" classtype, > > that would allow you to track/limit I/O and space usage for a set of > > directory hierarchies? > > Set of directory hierarchies in a regular (non-rcfs) filesystem ?
Yes. > > The directory hierarchy in rcfs represent CKRM classes and don't have > any correspondence to disk filesystem hierarchies. So I don't see how > you'll specify the directory hierarchy you're trying to regulate (if > thats what you're suggesting). I'd imagine it working something like: echo $somepath > /rcfs/directory/somegroup/members and then $somepath and all files/directories below it would be tracked. Probably done either by (ab)using the existing quota fields in the inode, or adding a list field to link each inode in to the CKRM class. There would probably need to be a restriction that no inode could be hardlinked between multiple directory classes. It could be done with existing group quotas, with a separate groupid created for each hierarchy, but that makes it trickier to use group permissions on the directories in question. Paul ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
