Hi,

I am running currently boinc_4.13_i686-pc-linux-gnu on my SuSE 9.2 box. It uses setiathome_4.02_i686-pc-linux-gnu to process the workunits.

After a short time the client sets its own priority to 39 which is far higher than any user process has. So even with a nice-value of 19 it steals so much CPU that it becomes a real pain to work with the computer.

A reasonable priority should be between 5 and 10. How can I change it to that value?

---

nice-values are from -20 (highest) to 19 (lowest) so 39 is normally impossible.
you will get an list of running programms by starting "top" in a xterm. press r to renice seti. it should already run with 19.

---

> nice-values are from -20 (highest) to 19 (lowest) so 39 is normally
> impossible.
> you will get an list of running programms by starting "top" in a xterm. press
> r to renice seti. it should already run with 19.
>

Don't confuse nice value with priority. You can only change the nice value. The kernel will use that to set priority. As long as the nice value is set to a high number (it defaults to 19), you'll be ok. The nice value will stay constant until you change it. The priority will vary depending on what else is going on at the time.

(You should also notice that the boinc core client actually runs with a nice value of 0, the norm for any user process. However, the particular application client (seti, lhc, climateprediction, etc) is the one that runs with a nice value of 19.)

Charlie

---

This is normal. Mine is running at nice = 19 and priority = 39. This means it's running at the nicest level (giving way to processes of higher priority). You shouldn't experience any slow down of your machine running at this level (well, at least I don't).

Ned

---

*** My Guide to Compiling Optimised BOINC and SETI Clients ***
*** Download Optimised BOINC and SETI Clients for Linux Here ***

The problem disapeared after a kernel-update from SUSe.
The new kernal does now respect the nice value.

---