[nsp] Suggestions on Versioning Control

jlewis at lewis.org jlewis at lewis.org
Tue Nov 18 22:28:02 EST 2003

On Tue, 18 Nov 2003, john heasley wrote:

> Tue, Nov 18, 2003 at 11:06:24AM -0500, Matt Stockdale:
> > We use Rancid (http://www.shrubbery.net/rancid/), which works well. It
> > doesn't run right on linux(redhat), or at least it didn't a few months
> it doesnt?  afaik, there are many redhat users running rancid.  in the
> past, linux folks who had troubles (which were not the result of user
> error) have almost always been the result of either 1) some eff'd-up
> rpm for expect/tcl, 2) some baroque nuance of linux.

Unfortunately, that "eff'd-up" expect/tcl rpm comes from Red Hat.  
Depending on which Red Hat version you're dealing with, worst case is you 
may have to patch/rebuild expect/tcl.  

Rancid's been an amazing tool.  Part configuration backup/versioning, part
change notification, part early warning "access-server is about to die" 
(as5200's tend to show partial configs when they've run low / badly 
fragmented their memory, and rancid notices this and emails us...at that 
point its either reload or wait for them to stop working).
Combine it with cvsweb, and even your non-unix/router-tech NOC people can
track down why a router broke and back out recent changes with ease.
 Jon Lewis *jlewis at lewis.org*|  I route
 Senior Network Engineer     |  therefore you are
 Atlantic Net                |  
_________ http://www.lewis.org/~jlewis/pgp for PGP public key_________

More information about the cisco-nsp mailing list