in reply to Perl ran SETI@Home for us.

I might be just completely blind, but here you use the array @seti:
&startSETI if ( ($uptime < $lowThreshold) && (______@seti______< $maxInstan +ces) ); # # if the uptime is above a certain load, # then kill a SETI instance. # &stopSETI if ( ($uptime > $hiThreshold) && (______@seti______ > $minInstan +ces) );
(emphasis with __s mine) But you never put anything in the array. Typo?

Anyways, thanks for this -- it's a great idea. I have a couple of machines with some unused CPU cycles, so I'll go ahead and install this.

Quinn Slack
perl -e 's ssfhjok qupyrqs&&tr sfjkohpyuqrspitnrapj"hs&&eval&&s&&&'

Replies are listed 'Best First'.
Re:x2 Perl ran SETI@Home for us.
by grinder (Bishop) on Nov 27, 2001 at 19:19 UTC
    @seti is being used in a scalar context here, to get the number of elements in the array. To be sure, it would have been better to use if( scalar @seti < $max ), but it is of no great import.

    To get a feel for how this works, you can play around with

    perl -le 'print @ARGV > 2 ? "more" : "less"'

    ... with more or less parameters following on the command line.

    update: oops, didn't realise this was a typo issue.

    --
    g r i n d e r
      I'm pretty sure that's not what qslack meant. @seti isn't declared anywhere. The author most likely meant to use @setiPids. use strict indeed.

      [ ar0n -- want job (boston) ]

Re: Re: Perl ran SETI@Home for us.
by rje (Deacon) on Nov 27, 2001 at 22:04 UTC
    You're absolutely right. Upon inspection, the
    array is probably @setipids (or was it @setiPids?).
    Thanks for the typo catch. You've got my vote for
    today.

    Rob