Sharku wrote:

baskitcaise <baskitcaise@hotmail.com> wrote:

If you are just using the machines for seti then leave at -19, upping
the nice will not make it run any faster as the machine will still
need to go about cron jobs and stuff so will take the cpu cycles when
it needs them, which means that you will only get the same cpu
allowance in one day.

If you do give seti a too high priority it can stop the rest of the
system from doing its own jobs and then you might be in a bit of a
hole :)

for max cpu time just prune down unwanted stuff from running and stop
as many of the cron jobs that you can afford.

If you want some responsiveness out of your system then you definately
don't want to set it to nice -19 (second highest priority). Personally I
wouldn't go any lower than -15 if you absolutely must give it a negative
nice, although I'd just put it on nice 0. If these machines are going to
be dedicated SETI machines, I don't think it'll make much difference
anyway, but by keeping your nice positive you don't risk locking
yourself out of your machine...

Just my .02 euro.

Sharku

Whoops my bad, sorry should not have had the "-" there, teach me for tryng to
do 2 things at once, old brain does not handle multi tasking as good as it
used to should stick to just -1 operation at a time :)

-- 
Mark
Twixt hill and high water.
N.Wales, UK.
Email is spam trap try baskitcaise at gmx dot co dot uk