[rancid] Re: Has anybody solved the extreme "unsaved changes" bug?

[john heasley]

Fri, Apr 23, 2010 at 10:21:42AM +1200, David Young:
> Hi all,
> 
> I refer to this issue:
> 
> http://www.shrubbery.net/pipermail/rancid-discuss/2009-January/003614.html
> 
> It seems that running RANCID against an extreme switch puts it into an
> "unsaved" state (maybe because of the clipaging?), and so while the
> first run is successful, any subsequent runs fail because of the
> asterisk in the prompt...
> 
> i.e.:
> 
> > > "expect -nobrace -re {* 300e48-x.([^#>\r\n]+)?[#>](\([^)\r\n]+\))?}
> {} -re {[
> > > ^M]+} { exp_continue }"

this should work; it used to.  we have one for testing but its not up yet.
send the o/p of clogin -d -s 'show version' host >log 2>&1.  that should
identify the issue.

i'd first make sure that you're using expect >= 5.43 and rancid 2.3.3.