Hi Andrew, Currently, modeguard does only enforce permission bits. It should be possible to make it evolve to also enforce group ownership. We thought about that at some point as we have been in the same situation as you for a while, and are still using modeguard to enforce the setgid bit as much as possible, but it’s not perfect (w.r.t rsync -a as you mention). So we’re now transitioning our last lustre filesystems to project (directory) quotas instead of group quotas. That way, group ownership doesn’t matter anymore for quotas. We found it much easier to manage and it's less confusing for our users.
Also… support for project IDs in Robinhood are in the works, patches are already available on GerritHub and we are running them in production. Now, we are just waiting for a new 3.x release... :) Best, Stéphane > On Nov 14, 2022, at 7:13 PM, Andrew Elwell <andrew.elw...@gmail.com> wrote: > > Is there a way to set modeguard (or equivalent) to set the group > ownership to (same as parent)? > > Our use case is that we apply per-group quotas for projects, and have > group sticky bits on /filesystem/projectcode/userid/ (which is owned > by userid:projectcode), however users have a habit of chgrp'ing to > their personal group id (thanks mostly to rsync -a) > Can modeguard prevent this- - I don't see anything likely in > https://github.com/cea-hpc/robinhood/blob/master/src/modules/modeguard.c > > Many thanks > > Andrew > > > _______________________________________________ > robinhood-support mailing list > robinhood-support@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/robinhood-support _______________________________________________ robinhood-support mailing list robinhood-support@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/robinhood-support
