I haven't seen any result size issues (and I've used it to run some commands with huge amounts of output), most of the time when I've run into problems with the result data being truncated, it has been due to my prompt() regexp being a little too simplistic, and it is matching something in the output. Be especially careful of prompts that contain dollar signs, $tn->prompt("foo$ ") will match anything that contains 'foo'...
What I usually end up doing when I need to parse output that may contain data that looks like the prompt, is to do something like this instead of using cmd:
my $tn = Net::Telnet->new();
# setup your connection here...
my $tag = "___END_OF_COMMAND___".time()."_".$$;
$tn->print("some command goes here ; echo $tag");
my($pre,$match) = $tn->waitfor( String => $tag );
my @output = split(/\r?\n/,$match);
Another option is to adjust the prompt on the remote server to be something you can readily identify that isn't likely to appear in your command output...
my $prompt = "___NET_TELNET_PROMPT_DETECTOR___".time();
$tn->cmd("export PS1=$prompt");
$tn->prompt("$prompt");
We're not surrounded, we're in a target-rich environment! |
---|
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|