sticky directory bit vs. loginfo chgrp

[Paul D. Smith]

Ok, I have an environment where lots of people have lots of different
CVSROOT repositories on the same system.

Each group has its own UNIX gid, and that's how I'm reserving
permissions: users who have permissions for a given repository are
members of the UNIX group; those who don't, aren't.

So, it's crucial that all adds and commits preserve the group
permissions on the files.  However, not every user has a primary group
which is the same as the repository.

I've seen one solution to this; you add something like this to your
CVSROOT/loginfo file for each repository:

  ALL chgrp -R <projgroupname> <repository>

This definitely works.

However, it seems like overkill to me.  I wonder why you couldn't just
use sticky bits on the repository directory?  Then all files and
subdirectories created in that hierarchy would automatically inherit the
gid of its containing (sticky bit set) directory, accomplishing the same
goal with much less work.

I tried it and in very limited testing it _seems_ to work.

Am I missing something?

-- 
-------------------------------------------------------------------------------
 Paul D. Smith <address@hidden>    HASMAT--HA Software Methods & Tools
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
   These are my opinions---Nortel Networks takes no responsibility for them.