Wow, that's fantastic. I hadn't even considered that approach. It's nice because the formatting of the output of
`ganglia proc_run` is conducive to being easily read with minimal reformatting effort.
Is there any considerable speed advantage to using the string instead of the array? Or does it have to do with memory usage?
Current form:
#!/usr/bin/perl
#Andrew Levenson
#4:14PM EST
#Friday, April 11th, 2008
#Displays nodes on Deli with 0 or 1 used processors
use strict;
use warnings;
my $zero = "\nZero Active Processors:\n\n";
my $one = "\nOne Active Processor:\n\n";
foreach ( `ganglia proc_run` )
{
$zero .= $_ if /\s0\s+$/ & !/deli/;
$one .= $_ if /\s1\s+$/ & !/deli/;
}
print "$zero$one\n";
C(qw/74 97 104 112/);sub C{while(@_){$c**=$C;print
(map{chr($C!=$c?shift:pop)}$_),$C+=@_%2!=1?1:0}}
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.