in reply to Re: problem with net::telnet moduleand STDOUT
in thread problem with net::telnet moduleand STDOUT

Hi

adjusting the max buffer did not work. By setting the value to a big number this stopped the server process spooling the output. Due to a system constraint it is not possible to create files on the remote system that is why I need to read the screen output to a file but first I need to overcome the more problem.

Cheers Nigel

  • Comment on Re^2: problem with net::telnet moduleand STDOUT

Replies are listed 'Best First'.
Re^3: problem with net::telnet moduleand STDOUT
by tachyon (Chancellor) on Jul 26, 2004 at 12:41 UTC

    Not knowing anything about the flow program all I can suggest it that it has a pager flag and in its interaction with Net::Telnet is delivering a virtual screenful. I don't definitively know how to fix flow or the Net::Telnet interaction. Regardless this hack should work around it. If I pipe a stream through more and then to cat:

    $ ll | more | cat

    Then more is effectively disabled as cat accepts the stream and just pipes it out so it streams several screenfuls. Certainly worth a try and I can't see why it will not work as we just abstracted the output from flow away from the vtty, but without using a file.

    Next suggestion is to try:

    $obj->option_accept( Dont => TELOPT_NAOP, Dont => TELOPT_NAWS ) # from the source we see the constants being declared..... # sub TELOPT_NAOP () {9}; # Output Page Size # sub TELOPT_NAWS () {31}; # Negotiate About Window Size

    If you dig into the souce you should find a burried use IO::Pty which does itself have a method to control the window size but no easy way to get at it short of hacking the source.

    cheers

    tachyon

      Hi

      Tried the option suggestion to no avail.Back to the drawing board.

      Thanks for your help, Nigel

        What about piping to cat? That kills more for me.

        cheers

        tachyon