I was unable to find an answer to my following question. I do have a work
around, however, I was hoping that someone else had insight on this. Please
help. :-)
I'm running cvs pserver on RH7.0... read xinted
My cvspserver config for xinetd looks like this:
service cvspserver
{
socket_type = stream
protocol = tcp
wait = no
user = root
passenv =
group = cvsroot
only_from = 192.168.200.0
log_type = FILE /var/log/xinetdlog
server = /usr/bin/cvs
server_args = -f --allow-root=/home/cvsroot/firmware pserver
log_on_success += USERID DURATION
log_on_failure += HOST USERID
disable = no
}
Note above that "group = cvsroot". All users with cvs access are members of
the group cvsroot.
Now...when a user adds a directory to an existing module, or imports a
module into the repository, the directories created get owner and group
privs for that user, and not cvsroot (as I had expected.) This causes
problems, since the umask is such that new directories are created with
775. Any user other than the one who added the directory cannot checkout
(or do any other cvs command) to that directory in the module. I then have
to manually log on as root and do a "chmod cvsroot.cvsroot" on the newly
added directory.
Why did cvs not change the group to "cvsroot"?
I am using the workaround by manually doing a chmod g+s on newly imported
modules, however, there's got to be a better way. Or is this something CVS
does not handle? I was under the impression that since CVS runs as suid,
and group=cvsroot (from xinetd) that any newly created directories (or
files for that matter) would have a group id of cvsroot.
Any insight and/or help on this is greatly appreciated.
Regards,
-Anders.
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
