The Linux Administration group is for the discussion of technical issues technical issues that arise during the administration of Linux systems, including maintaining the operating system and supporting end-user applications.

Popular White Paper On This Topic

Here is what I did...keep in mind that I don't use :pserver: auth
method, I use ssh. I think this covers everything, but I did this over
a year ago so I may have missed a step.

1) sent email to team letting them know the repository was moving. gave
them the new server name and time the system would be up again.
**Performed migration late at night**
2) renamed repository location on original server to "/CVS/oldcvsroot".
this prevented users from connecting since their clients were looking
for: /CVS/cvsroot.
3) recursively copied contents and preserved permissions of oldcvsroot
to cvsroot location on new server using scp.
4) made sure that unix security groups used to secure various modules
were on the new server and /etc/group was updated. I wrote a script to
sync this info on the new server.
5) tested CVS access with my regular user id
6) sent email notifying team that new repository was ready
7) unmounted /CVS on old server

Users simply changed the servername in their CVS client and were up and
running again.

Copyright 1998-2015 Ziff Davis, LLC (Toolbox.com). All rights reserved. All product names are trademarks of their respective companies. Toolbox.com is not
affiliated with or endorsed by any company listed at this site.