"Jim.Hyslop" wrote: > > Todd Denniston wrote: <SNIP> > > If I had to have a section where all my staff could > > read/write a section of > > the repo and co-ops could read/write that section as well, I > > would probably > > make group staff a member of group coops, and set that > > section of the repo to group coops. > Well, according to our sysadmin, a group can only have users as members - a > group cannot contain another group. That seems like a major shortcoming to > me, but that's what I'm told. >
You know I thought I had that working, but going back and checking it now, it seems your sysadmin is correct. darn. <SNIP> > - Each user has a default group that is used to set permissions on new files > (I know there's supposed to be a way to configure the O/S to inherit > permissions from the parent, but our sysadmin either hasn't figured it out > or is too busy to correct the problem). This is the problem that I was originally covering in this thread. :) check my message from '28 Mar 2005 16:05:51 -0500' -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter _______________________________________________ Info-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/info-cvs
