[rancid] Re: f5 bigIP part 2

[john heasley]

Wed, Feb 04, 2009 at 08:06:42AM -0600, kenneth.w.sain at accenture.com:
> I'm not sure how that would be accomplished.
> 
> f5rancid contains no expect send commands, it calls clogin to handle
> that work.  I have no idea where or how I'd accomplish this inside
> bin/f5rancid.
> 
> Interestingly, f5rancind does contain the lines:
> # force a terminal type so as not to confuse the POS
> $ENV{'TERM'} = "vt100";
> 
> But it doesn't seem to have any affect on the login process.

telnet/rsh/ssh, variables such as TERM are normally exchanged with the
server/daemon.  so, why isnt it happening here?

> I did find that some of the @commandtable entries had syntax errors for
> the older 4.5 bigIP code.  Commenting those out and using the vt100 hack
> in clogin is working for me now.

is that the old code?  I was told by another user that the old code has
antiquated and that folks could just upgrade.  I'd rather not support
the old code.

>  
> Ken Sain
> Accenture @ MyFloridaMarketPlace
> (850) 414-7580 (office)
> (850) 508-4227 (cell)
> kensainwork on Yahoo/AOL IM
>  
> 
> -----Original Message-----
> From: john heasley [mailto:heas at shrubbery.net] 
> Sent: Tuesday, February 03, 2009 10:16 PM
> To: Sain, Kenneth W.
> Cc: mashcraft at omniture.com; rancid-discuss at shrubbery.net
> Subject: Re: [rancid] Re: f5 bigIP part 2
> 
> Tue, Feb 03, 2009 at 03:50:42PM -0600, kenneth.w.sain at accenture.com:
> > Hrm, I already hardcoded clogin to provide vt100, just like the other
> > poster in the URL I provided.  And I've confirmed that it works via a
> > bin/clogin bigip01.
> 
> any change like setting TERM should be done in f5rancid, NOT clogin.
> Let
> clogin inherit it.
> 
> 
> 
> This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information.  If you have received it in error, please notify the sender immediately and delete the original.  Any other use of the email by you is prohibited.