[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: twisted CVS
RE: twisted CVS
Wed, 14 Aug 2002 04:17:16 -0700 (PDT)
--- Piet Verhoeve <address@hidden> wrote:
> thanks for the tip, however it doesn't seem to work.
> I did set the SGID bit (chmod -R uga+g /dev ) on all
The command I'm familiar with is "find $CVSROOT -type
d | xargs chmod g+s". I don't know what system you
have so man chmod to make sure you're doing the right
In any case, I have two comments on the command above:
1. "chmod -R" will chmod files as well as directories.
In general, this is not what you want. In CVS, I
think this may not have any major impact.
2. Why are you chmod'ing /dev? IMO, it's highly
irregular to have the repository within /dev.
Oh, yeah, before I forget, you'll need to own the
file/directory before you're able to chmod it.
> Consequently one user performed cvs edit on a file
> and another did the same
> thing on another file. The second user got the "cvs
> server: cannot write
> .../CVS/fileattr" message.
> Upon check in the repos. the CVS directory had
> indeed the settings rw for
> user1 only (both as owner and group ownership) and
> read only for all users
> (i.e. rwxrwxr-x). The thing is that I should be able
> to perform the chgrp or
> the chmod after the execution of the cvs edit
> command (like I can do after a
A comprehensive pre- and post- trigger architecture
has been on my wish list for some time. I don't think
it's coming any time soon.
In you're particular situation, the alternative is to
get the permissions correct from the start.
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs