[rancid] Re: Foundry ServerIron

[William Yardley]

On Tue, May 12, 2009 at 02:48:03PM -0700, john heasley wrote:
> Tue, May 12, 2009 at 02:42:00PM -0700, William Yardley:
> > On Tue, May 12, 2009 at 02:34:20PM -0700, john heasley wrote:
> > > > raw output from 'francid hostname.example.com' shows:
> > > > 
> > > > hostname.example.com
> > > > spawn ssh -c 3des -x -l rancid hostname.example.com
> > > > rancid at hostname.example.com's password: 
> > > > SSH at hostname>
> > > > [hangs there]
> > > 
> > > if its autoenable, the prompt should end with '#'.
> > 
> > Yeah - then I guess it's noenable I want rather than autoenable. Any
> > chance this is broken with foundry stuff on 2.3.2a10, or am I screwing
> > something else up?
> 
> i dont think so.  it should enable next, be sure that it does that and
> and flogin -c 'show vers;show vers' works
 
It should enable even when 'noenable' is set (and autoenable is not
set)? The thing I'm saying might be a bug is the fact that noenable
seems to be getting ignored in .cloginrc (with flogin, but *not*
clogin).

Just to make sure we're talking about the same thing, the device in
question should happily do the commands needed *without* enabling at
all. I belive 'noenable 1' is what I need to set for that. As I said,
running flogin with -noenable works Ok, but flogin with noenable set in
.cloginrc spits out an error.

FWIW, "flogin -noenable -c 'show vers;show vers'" works fine.

> > RHEL 4u7, RPM of rancid built from the included specfile, Expect is
> > version expect-5.42.1.
> 
> and the expect patch available on the rancid web site.

Oh - that may be part of my problem -- I had thought the expect patch
was only necessary with versions of expect < 5.40, but just realized
that that's not the case.

w