[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Changing CVS repository name

From: Lars Thuring
Subject: Re: Changing CVS repository name
Date: Thu, 30 Oct 2003 09:32:33 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425

address@hidden wrote:
Hash: SHA1

Lars Thuring wrote:

| Also we did not find a solution to multi-user access control to
different modules so we are skipping that. The NFS mount point will only
be used by a cron command to do the nightly backup of the repository.

That's just a matter of using standard UNIX user and group permissions.
You need to use a LockDir with write permissions for everybody if
anybody has read-only access to any projects.  Otherwise users who are
supposed to have read-only access can't even read since they don't have
permission in the repository project dirs to create lock directories and

That is what we tried but we did not make any special provisions for the LockDir.

What we did to test this was to create a user "cvs" (also with a group with the same name) which owned all the directories in the /data hierarchy, so that owner and group of all files was set to "cvs". Using CVSROOT/passwd to set cvs user id to "cvs" worked ok so we then added individual users here, like "cvslth". "cvslth" was also a member of the group "cvs" using group access settings. We had imagined that would work, but it did not. All rights within /data was "rwxrwxr-x" for files and dirs.

Is there an example on how to do this somewhere online? We could also live with using several repositories on the same server, but this doesn't seem possible as there is only one /etc/xinetd.d/cvspserver file on the server stating where the repository lies, right? The texts on multiple repositories we have found all talk about checking out from different server to the same directories on the client which is not what we want.

best regards,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]