|
in reply to launch xterm for STDIO to perl script for telnet
I'm not sure I'm understanding your write-up, so I'll attempt to clarify. Why are you spawning an xterm in a child process, which connects via TCP back to its own parent, and having the parent do the connection to the router? Why don't you have the spawned child run a connection script on its own which connects directly to the router, not going through the parent? You would still need Expect.pm, but once the interactive login is complete, piping stdin/stdout to your router connection should be trivial.
I think I am missing something.
|
