StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POCan I use symbolic links for cvs root to simplify server consolidation?
primarykey
Id
622064
data
AcceptedAnswerId
622082
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-03-07T16:20:33.647
FavoriteCount
0
LastActivityDate
2013-03-28T07:55:34.540
LastEditDate
2009-03-20T07:42:34.203
LastEditorUserId
15168
OwnerUserId
72150
ParentId
0
PostTypeId
1
Score
1
ViewCount
1620
LastEditorDisplayName
Jonathan Leffler
text
Body
We're consolidating two old cvs servers onto one new box. I had hoped the following: changing the dns entries for oldserver1 and oldserver2 (as well as some user account maintenance) would make the move transparent to cvs users. Problem: I'm having problems due to the different cvs roots on each old server. Background The old servers had the following cvs repository directories: <ul> <li>old server1 cvs root: /cvshome</li> <li>old server2 cvs root: /usr/local/cvs</li> </ul> On the distribution we're using the default repository directory is /var/cvs. I opted to stick with this, i.e: <ul> <li>new server cvs root: /var/cvs</li> </ul> Goal I'd like minimal disruption on existing checked-out-projects, i.e. not having to find/replace all 'Root' files on each hard drive in the company. To clarify, CVSROOT and CVS/Root entries for old server1 look like this: <pre><code>pserver:username@oldserver1:/cvshome </code></pre> Attempts I tried this: create a symbolic link on new server <pre><code>/cvshome points to /var/cvs ln -s /var/cvs /cvshome </code></pre> However, when I try an update (i.e. from a workstation that pointed to old server 1), I get this error: <pre><code>/cvshome : no such repository </code></pre> Summary Can I use links to 'alias' a cvs repository? OR do I need to 'bite the bullet' and change all 'Root' files on all hard drives? thanks, bill
Tags
<cvs><symlink>
Title
Can I use symbolic links for cvs root to simplify server consolidation?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USJonathan Leffler
UserOwnerUserId
1. USuser72150
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POCan I use symbolic links for cvs root to simplify server consolidation?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.