Hi,

after the last few days without work I finally got some units and got my CPU busy again. A little bit too busy.

I updated my boinc-client to boinc_5.8.17_x86_64-pc-linux-gnu and my S@H-client to KWSN-R2.2B-64bit-SSE2-generic. Starting is done via init-script and start-stop-manager on a Gentoo Linux box.
No matter what how I start the Boinc-Client, via script or directly on the console I get the following behaviour:
In the script a nicelevel of 19 is set and the Boinc-Client perfectly starts up with that level. But the S@H-client simply seems to ignore this and starts with level 0. When I manually set it to 19 it "resets" itself to 0 on the next WU.
I couldn't find anything why the client behaves that way. The old client I had (5.1* as far as I remember) started the S@H-client with the same nice-level I defined for himself.

Can someone give me a hint where to search or how to solve it? Please don't refer to google and RTFM... I already searched there. ;)

Thanks so far
Loci

No matter what how I start the Boinc-Client, via script or directly on the console I get the following behaviour:
In the script a nicelevel of 19 is set and the Boinc-Client perfectly starts up with that level. But the S@H-client simply seems to ignore this and starts with level 0. When I manually set it to 19 it "resets" itself to 0 on the next WU.

Well, when I came back to BOINC a few weeks ago, I emerged boinc and that gave me 5.8.15 which worked fine. Since then, I have been using the SVN sources (5.9.*) which also work fine for me. I never did use 5.8.17 AFAICR.That would seem to suggest a problem with that particular version.

---

Be lucky

Neil

Hi,

after the last few days without work I finally got some units and got my CPU busy again. A little bit too busy.

I updated my boinc-client to boinc_5.8.17_x86_64-pc-linux-gnu and my S@H-client to KWSN-R2.2B-64bit-SSE2-generic. Starting is done via init-script and start-stop-manager on a Gentoo Linux box.
No matter what how I start the Boinc-Client, via script or directly on the console I get the following behaviour:
In the script a nicelevel of 19 is set and the Boinc-Client perfectly starts up with that level. But the S@H-client simply seems to ignore this and starts with level 0. When I manually set it to 19 it "resets" itself to 0 on the next WU.
I couldn't find anything why the client behaves that way. The old client I had (5.1* as far as I remember) started the S@H-client with the same nice-level I defined for himself.

Can someone give me a hint where to search or how to solve it? Please don't refer to google and RTFM... I already searched there. ;)

Thanks so far
Loci

Hi All,

I am having the same problem as Loci but with boinc client 5.8.16 for Linux/x86 and 5.10.2 for Linux/x86, S@H client KWSN-R2.2B2-SSE2-P4 running on Ubuntu 6.10 and i have to do the same thing and manually set the S@H client to nice 19 every time it starts a WU.

---

Cheers Quail

What happens, if you start the BOINC client directly from the command line (with ./run_client from within the BOINC client directory) ?

---

What happens, if you start the BOINC client directly from the command line (with ./run_client from within the BOINC client directory) ?

The Linux apps for 2.6 kernel have a build in shedular /priority code wich will set them on "0" as nice level.

The only way to avoid that is to use an app for 2.4 kernel.

---

Join BOINC United now!

The Linux apps for 2.6 kernel have a build in shedular /priority code wich will set them on "0" as nice level.

The only way to avoid that is to use an app for 2.4 kernel.

Huh? How do you make an application dependent on a specific kernel version?
Surely once any linked library version requirements have been satisfied the kernel version should be irrelevant.
Or are you referring to an application which is old enough to expect only library versions as would have been provided with kernel 2.4?

---

To err is human; to moo, bovine.

The Linux apps for 2.6 kernel have a build in shedular /priority code wich will set them on "0" as nice level.

The only way to avoid that is to use an app for 2.4 kernel.

Huh? How do you make an application dependent on a specific kernel version?
Surely once any linked library version requirements have been satisfied the kernel version should be irrelevant.
Or are you referring to an application which is old enough to expect only library versions as would have been provided with kernel 2.4?

2.2B for kernel 2.6 is able to set cpu priority and affinity while running it's initial bench for best functions.

2.2b for kernel 2.4 is not able to do that. Mainly for backwards compatibility.

hth

---

Join BOINC United now!

2.2B for kernel 2.6 is able to set cpu priority and affinity while running it's initial bench for best functions.

2.2b for kernel 2.4 is not able to do that. Mainly for backwards compatibility.

Oops, sorry - you meant 'seti' but I thought 'generally'.

Thanks - it's still useful to know.

---

To err is human; to moo, bovine.

2.2B for kernel 2.6 is able to set cpu priority and affinity while running it's initial bench for best functions.

2.2b for kernel 2.4 is not able to do that. Mainly for backwards compatibility.

Oops, sorry - you meant 'seti' but I thought 'generally'.

Thanks - it's still useful to know.

No need to be sorry ;)

---

Join BOINC United now!

Hi All,

I am having the same problem as Loci but with boinc client 5.8.16 for Linux/x86 and 5.10.2 for Linux/x86, S@H client KWSN-R2.2B2-SSE2-P4 running on Ubuntu 6.10 and i have to do the same thing and manually set the S@H client to nice 19 every time it starts a WU.

I wrote a small shellscript which renices Seti every 5 minutes per cron. It's only a quick&dirty workaround... but it helps...

---

I wrote a small shellscript which renices Seti every 5 minutes per cron.

I would love a copy, if it would work with OS.X...

---

ad astra with slack

I did find (for OS.X) 2 progs: Renicer & BeNicer -
Renicer is inexpensive and works for most normal apps, but does not find Boinc projects (however, it does do persistent renicing or auto renicing of front-most apps, neither of which BeNicer does);
BeNicer is much more thorough (tho it's free and about 4 years old) and finds any app as long as you know which user is running it (the user "boinc_projects" is found in the list of users shown by NetInfoManager), then it's simple to speed all the way up to -20, or down to 20 (the change is persistent only until Boinc restarts the project, but that it not much of a bother).
Both progs are at VersionTracker.com...

---

ad astra with slack

the change is persistent only until Boinc restarts the project, but that it not much of a bother

Spoke too soon - Boinc reniced the project after all.
:^(
Still need a permanent fix!

---

ad astra with slack

I wrote a small shellscript which renices Seti every 5 minutes per cron.

I would love a copy, if it would work with OS.X...

The script is using /usr/bin/renice... and I have no clue if this somethin similar exists for OSX. The script is rather simple.... "pidof" determines the pid of Seti and renice does the renicing of this pid.

---