[rancid] reason for autoenable?

[Lee]

On 8/27/10, john heasley <heas at shrubbery.net> wrote:
> Fri, Aug 27, 2010 at 09:35:01AM -0400, Lee:
>> On 8/26/10, john heasley <heas at shrubbery.net> wrote:
>> > Thu, Aug 19, 2010 at 03:04:25PM -0400, Lee:
>> >>   ... more newbie questions
>> >>
>> >> If the userid automatically gets priv level 15 at login and you forget
>> >> to set the autoenable flag the clogin script times out waiting for the
>> >> ">" prompt.  Why was the autoenable flag added instead of changing the
>> >> expect script to look for # or >?  It seems nicer not to require a
>> >> flag...
>> >
>> > i'll blame Hank again.  autoenable just simplifies the code by moving
>> > the
>> > burden.
>> >
>> > I have a patch to remove it, but it still wants to enable.  i'd like
>> > poeple
>> > to test before its is committed.  see attached.
>>
>> I'll be glad to give it a try; I need to apply the patch to clogin.in
>> and then do a "make && make install" - correct?
>
> either clogin or clogin.in; the patch affects nothing that is replaced by
> the autoconf process.

Works for me :)

I patched clogin & had no problems with a
  clogin -c "sh int status err" $DEV
on various IOS switches at work.  We don't have any CatOS switches, so
I couldn't test that.

Thanks,
Lee