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}}
-
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.
|