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

[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 }"

Thanks :)
David