Re: sticky directory bit vs. loginfo chgrp

[Laine Stump]

"Derek R. Price" <address@hidden> writes:

> Laine Stump wrote:
> 
> > So what's the best way to make sure that every new file and directory
> > in the repository has g+w? (Aside from telling everyone to set their
> 
> What happens if you set UMASK from inetd?

Nevermind. I seem to be imagining problems where they don't exist. I
just tried it out again and this is what happens:

 * if a directory is created with "cvs add dirname" it will be created
   with the group of the parent (in the repository), and group write
   permission turned on, regardless of the user's umask.

 * if a file is created with "cvs add file; cvs commit", it will be
   created with the group of the parent, and mode 444. However, since
   the directory that contains it has g+w, cvs can get around this
   when another user attempts to modify it by doing the equivalent of:

           cp file,v temp
           rm file,v
           mv temp file,v

   (I don't know if that's what CVS does, but it works and proves
   that proper operation is possible)

So, now that I understand what's going on, there is no problem ;-)