[lug] replacing login shell

[Chip Atkinson]

It depends on the complexity of the telnet session, but you may wish to
consider either expect or the expect perl modules.

One of the best things about expect is that you can control the speed at
which characters are sent.  This is very important in some situations
because most of the characters that are just blasted at the speed of a
bash here document come so fast that they get lost.

Chip

 On 25 Jun 2002, Hugh Brown wrote:

> I have tasked with creating a replacement login shell to force telnet to
> another machine.
>
> We have a web applet that uses jta to login via ssh (no keys) to a
> system.  when it logs in we want it to start up telnet to a legacy host
> that only accepts telnet.
>
> what is the right way to do it?
>
> I was looking at writing a bash script that trapped all signals and
> started up a telnet session.
>
> Are there any gotchas I should watch out for?
>
> Hugh
>
>
>
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: lug.boulder.co.us port=6667 channel=#colug
>