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

David Young david at prophecy.net.nz
Thu Apr 22 22:21:42 UTC 2010

Hi all,

I refer to this issue:


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...


> > "expect -nobrace -re {* 300e48-x.([^#>\r\n]+)?[#>](\([^)\r\n]+\))?}
{} -re {[
> > ^M]+} { exp_continue }"

Thanks :)

More information about the Rancid-discuss mailing list