info-cvs
[Top][All Lists]
Advanced

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

Re: move cvs from solaris to solaris


From: Todd Denniston
Subject: Re: move cvs from solaris to solaris
Date: Wed, 22 Feb 2006 14:03:14 -0500
User-agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929)

Please keep responses on the list too, they may help someone else in the future, and/or get answers to your further questions. :)

Peter marshall wrote:
THanks for the detailed reply.  I will have to read up on pserver .. I do
not know much about it.

I started looking into the repository Directories and did see the CVSROOT
directory in each.  It looks like there is a passwd file in each.  I edited
the file and the file containes a number of usernames, encrypted passwd, and
then cvs.

ex:
username:blahblahblah:cvs

I am not sure what the cvs tag at the end does, but it does appear that the
password is comming from the shaddow file (which I just found out that
someone coppies in by hand).  Is there another way to generate an encrypted
password that the password file will be able to read so that I do not have
to create local users on the unix box first ??


There are a couple of tools available but I do not remember their names.
The list archive can probably help though.

http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=pserver+password+program&submit=Search%21&idxname=info-cvs&max=20&result=normal&sort=score
http://lists.gnu.org/archive/html/info-cvs/2001-03/msg00027.html

Thank you again for your detailed help.

Peter

On 2/22/06, Todd Denniston <address@hidden> wrote:

address@hidden wrote:

I have a couple of questions.

My current situation is I started working at a company with a solaris 8
box that has a cvs repository on it.  The box is old is being replaced
by a muh newer box.  The long and the short of it is that I need to get
cvs off of the old box and onto the new box.

The problem, ... I have never used or worked with cvs ... ever.

You then should probably issue full stop to your other questions for a
short
period of time and see my answer to your question #4.

BTW looks like you did an OK job analyzing your current setup.


What I think I know:
CVS runs on the solaris box as the cvs user.
It is started as part of the inetd service.  (entry below)
cvspserver      stream  tcp     nowait  cvs     /usr/local/bin/run.cvs

The run.cvs file sets a variable that contains all of the repositories,
and then runs the following
exec /usr/local/bin/cvs -f $myrepository pserver

the myrepository variable looks something like this
myrepository="--allow-root=/cvs/repository1
--allow-root=/cvs/repository2 ..... "

The /etc/services file has the following 2 entries
cvspserver      2401/tcp
cvspserver      2401/udp

** Currently, the server running cvs is on a unix domain.  The new
server will not be on a unix domain.

Now .. Getting slightly more comlicated, and more into the unknown.
How are the users for cvs created.  From the reading I did, it looks
like they might be somehow created from the passwd file.  It is my
intention to not create a username on the unix server for every user
that has access to cvs.

Question1.  Is there a way to create users in CVS without using the
/etc/passwd or yppasswd files?  If so, How.

Yes. LDAP ...:) or using cvspserver[3][4] itself.
LDAP: you will have to look up yourself (not sure but you might even be
able
to use an MS server for username/password with LDAP, though I think most
of us
would have the MS machines authenticate using a Unix LDAP server instead).

cvspserver: you will have to maintain a CVSROOT/password file for each
--allow-root listed in your run.cvs script, and AFAIK they will have to be
maintained by hand as cvspserver does not allow for the setting/updating
of
passwords through the pserver protocol.


Question2.  How do I get the cvs user accounts from the old server to
the new server.

If they are already in CVSROOT/password files, then as you tar -> untar
the
repositories from one machine to the other they come along for the ride.

if they are in /etc/[passwd/shadow] you need to bring relevant portions of
those files along (be careful)... but you indicated you did not want to
use
/etc/passwd.

if the are in NIS/LDAP, configure your new server to authenticate against
the
NIS/LDAP server and you are done... but you indicated you did not want to
use
yppasswd.


Question3.  As far as transfering the CVS repository from one server to
the other, can I just tar up the directory, and transfer the tar file ?


pretty much, see what the manual has to say[2].


Question4.  What else am I missing.

A copy of the manual[1] for local reading, read it all if you are going to
be
the admin.  It's text may not keep you awake at night (unless pserver
scares
you, and it should), but it will help you do your job correctly.

If pserver does not scare you, then either you have a superb firewall, or
when
lists.gnu.org comes back up you might need to do a search on the words
pserver
 AND security.


Thank you for your help.


[1] http://ximbiot.com/cvs/manual/
[2] http://ximbiot.com/cvs/manual/cvs-1.11.21/cvs_2.html#SEC25
http://ximbiot.com/cvs/manual/cvs-1.11.21/cvs_2.html#SEC24
[3] http://ximbiot.com/cvs/manual/cvs-1.11.21/cvs_2.html#IDX81
[4] http://ximbiot.com/cvs/manual/cvs-1.11.21/cvs_2.html#SEC32



--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter




reply via email to

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