Mark D. Baushke wrote:
The only problem now is that if a cvsadmin user introduces a directory
into the cvs repository using "add", the directory is owned by him, not
by the global cvs user, and nobody else can check into/out of that
directory.
How do I automatically force new directories created by the cvs server
to be owned by the global cvs user, rather than the effective user?
This is the wrong question.
why is that? Maybe I should be talking group here not owner?
You could have the directories all be in a 'cvs' group and use
find $CVSROOT -type d -exec chgrp cvs g+s {} \;
find $CVSROOT -type d -exec chmod g+s {} \;
The cvs user could belong to this group 'cvs' as well as your admin
users. New files and directories created will inherit the groupid of the
parent directory. A crontab job could go thru and change the ownership
of the files and directories in the tree to that of the 'cvs' user on a
periodic basis as additional cleanup if desired.
g+s is not a valid arg for chgrp. what did you really mean here?
my admin users do already belong to the cvs group, as do all the
repository directories.
I think what you're effectively saying here is that by setting sticky on
the directories, then new directories are created group cvs, and owner
is not important. Is that right?
j.
_______________________________________________
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs