I would run the script from the command line before testing in a browser window, then printing the input or output of aml_read is simple and might display errors not shown in the browser. That first for loop can be more perlish:
for my $i ($TTYFIRST..$TTYLAST) {
Tty_check($i,$start_ts,$end_ts,$selectedserver);
}
That script doesn't seem well thought out, if you're searching for 'tty1' it'll count lines with 'tty17' also. Depending on the format of the output of that aml_read command (minus the pipe to egrep), I might use perl's
split function, so that I could do something like:
my %ttys;
for $line (`aml_read /l trace /h $_[3] /a commproc /s $_[1] /b $_[2]
+/d all`) {
# I'm making this split up, you'll have to post the
# format of aml_read or figure out the split yourself
my ($something, $tty, $stuff) = split " ", $line;
$ttys{$tty}++;
}
for my $tty (sort { $a <=> $b} keys %ttys) {
print "Count for $tty: $ttys{$_}\n";
}
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.