info-cvs
[Top][All Lists]
Advanced

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

Re: Changing CVS repository name


From: Derek Robert Price
Subject: Re: Changing CVS repository name
Date: Thu, 30 Oct 2003 09:54:32 -0500
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Lars Thuring wrote:

| 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.


Did you chmod g+wrx /data or chmod -R g+wrx /data?  What error messages
were you seeing?

| 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.


You could set them up as different --allow-root options to your cvs
server executable in /etc/xinetd.d/cvspserver

Derek

- --
~                *8^)

Email: address@hidden

Get CVS support at <http://ximbiot.com>!
- --
If genius is one percent inspiration and 99 percent perspiration, I
sure wind up sharing elevators with a lot of bright people.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org

iD8DBQE/oSYnLD1OTBfyMaQRAlwKAKDo5GoXZ4PsaTd4BelPx9cD4vIEOwCggXEC
Zd6v+Zlr9xDkL9WaQ9uPbJw=
=hJOB
-----END PGP SIGNATURE-----






reply via email to

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