[rancid] Installation problem with rancid-cvs

[David Willson]

I'm installing rancid on a new box running Fedora 10 and come across an issue when it comes time to run the rancid-cvs command.



I've been following this guide: http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_:_Ch1_:_Network_Backups_With_Rancid



First time around when I ran the rancid-cvs command I got an error about how cvs was unknown. A quick 'yum install cvs' fixed that up, so I ran it again. This time however I got no output at all, no error messages or confirmation text, just a new line and new command prompt, it didn't appear to do anything.



I also checked to see if any of the folders had been created, they haven't.



Thinking it may have been an issue with cvs not being installed from the start, I did another recompile/reinstall, but got the same issue, when I ran rancid-cvs nothing appeared to happen at all.



How would I go about diagnosing/fixing this? Anyone familiar with the issue? I'm installing the latest a9 version.

_________________________________________________________________
Who's buying you chocolate this easter? Find someone to be sweet to you at Match.com
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fdating%2Enz%2Emsn%2Ecom%2Fchannel%2Findex%2Easpx%3Ftrackingid%3D1048628&_t=773568480&_r=nzWINDOWSliveMAILemailTAGLINES&_m=EXT

[David Willson]

Running make uninstall and starting again from the 'configure' part of the guide still results in the same problem, is there something I can do to make sure I'm properly uninstalling everything?



From: ***@rn.dk
To: ***@hotmail.com
Date: Tue, 17 Mar 2009 21:32:57 +0100
Subject: SV: [rancid] Installation problem with rancid-cvs




I had the exact same problem, I reinstalled everything and then it worked fine.
I'm using CentOS5 but that should be more or less the same.

/Arne



Fra: rancid-discuss-***@shrubbery.net [mailto:rancid-discuss-***@shrubbery.net] På vegne af David Willson
Sendt: 17. marts 2009 20:26
Til: rancid-***@shrubbery.net
Emne: [rancid] Installation problem with rancid-cvs


I'm installing rancid on a new box running Fedora 10 and come across an issue when it comes time to run the rancid-cvs command.

I've been following this guide: http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_:_Ch1_:_Network_Backups_With_Rancid

First time around when I ran the rancid-cvs command I got an error about how cvs was unknown. A quick 'yum install cvs' fixed that up, so I ran it again. This time however I got no output at all, no error messages or confirmation text, just a new line and new command prompt, it didn't appear to do anything.

I also checked to see if any of the folders had been created, they haven't.

Thinking it may have been an issue with cvs not being installed from the start, I did another recompile/reinstall, but got the same issue, when I ran rancid-cvs nothing appeared to happen at all.

How would I go about diagnosing/fixing this? Anyone familiar with the issue? I'm installing the latest a9 version.



Find someone to be sweet to you at Match.com Who's buying you chocolate this easter?
_________________________________________________________________
Find a way to cure that travel bug with MSN NZ Travel
http://travel.msn.co.nz/

[David Willson]

BINGO! deleting the CVS and networking (group) folders from /usr/local/rancid/var/ allowed rancid-cvs to run as intended, thank you!

you probably have some turds left behind. remove the CVS dirs under
/var/rancid (or whereever it ended-up); move the group dirs aside; run
rancid-cvs.

_________________________________________________________________
Looking for a place to manage all your online stuff? Explore the new Windows Live
http://www.windowslive.com/Explore

[john heasley]

Post by David Willson
BINGO! deleting the CVS and networking (group) folders from /usr/local/rancid/var/ allowed rancid-cvs to run as intended, thank you!

you probably have some turds left behind. remove the CVS dirs under
/var/rancid (or whereever it ended-up); move the group dirs aside; run
rancid-cvs.

WARNING: this is only the solution because he's just begun. Do not do this
with a previously functioning installation.