Firstly a huge thanks for porting the linux apps. Much appreciated.

Secondly you might be interested to know that here in Australia, the demand for PS3s was so low there was more media and security than customers at launch...!

I think it's because the price here after conversion seems way more than it should, combined with the fact we miss out on hardware PS2 support... I sure won't be getting one as soon as I had originally thought.

And, thanks for the apps again!

---

Crunching SETI@Home as a member of the Whirlpool BOINC Teams

Back on topic :o)

Linux Rev-2.2B apps have been released -

Go grab yours!

Happy Linux crunching,
Simon.

---

Donate to SETI@Home via PayPal!

Optimized SETI@Home apps + Information

Back on topic :o)
Linux Rev-2.2B apps have been released
Simon.

After changing to above (thanks once again for that), my seti client priority changed from 19 to 0.
Is it a normal situation?

---

Back on topic :o)
Linux Rev-2.2B apps have been released
Simon.

After changing to above (thanks once again for that), my seti client priority changed from 19 to 0.
Is it a normal situation?

I just installed them, restarted and priority is still 19, on all 4 of my linux machines.
You could just renice the task with top. I doubt it is permanent.

My machine is also now running the kwsn app as nice 0 instead of 19.
How does one renice using top? And are changes done this way permanent?

---

Crunching SETI@Home as a member of the Whirlpool BOINC Teams

My machine is also now running the kwsn app as nice 0 instead of 19.
How does one renice using top? And are changes done this way permanent?

run top, find the pid of the task(s) (sort using 'M' for memory usage and it should stay near the top), press 'r' then enter the pid, then enter the nice value 19 and it is done.
Unfortunately this will only work for the lifetime of the task.

BOINC should automatically set it to 19, I've never seen it do otherwise, so I think restarting BOINC should fix it permanently.

Cheers, it re-niced fine.
I restarted BOINC before running the app, but haven't restarted since then. Since this is an always-on machine, it could be a while!
Although I'll probably just try restarting tomorrow, time to leave work now : )

---

Crunching SETI@Home as a member of the Whirlpool BOINC Teams

Good Job Chicken! Just looking at the initial changes I got for running ver 2.2B, looks like got a 40% improvement on speed from vers. 1.3. Will have to wait till all the validatation backlogs clear to really see the improvement.

The apps do run with higher priority while doing function benchmarks at the start of WUs. After that, they should run at idle priority (19) again on their own.

HTH,
Simon.

---

Donate to SETI@Home via PayPal!

Optimized SETI@Home apps + Information

Cheers, it re-niced fine.
I restarted BOINC before running the app, but haven't restarted since then. Since this is an always-on machine, it could be a while!
Although I'll probably just try restarting tomorrow, time to leave work now : )

Forgive me if this is obvious... It can stay an "always on" machine. Restarting boinc is not the same thing as rebooting! You should only ever need to restart linux after installing a new kernel or making hardware changes, or after doing something stupid while developing!

I turned boinc into a service running as its own user, so restarting is as easy as /etc/init.d/boinc restart, or service boinc restart. That way if I do have to reboot for a kernel upgrade then I don't have to worry about doing anything else.

If not running as a service, then
./boinc_cmd --quit
followed by
./boinc_client >>log.txt 2>>error.log &
should be enough.

Andy.

Forgive me if this is obvious... It can stay an "always on" machine.

BOINC runs as a startup script for me, and sometimes I'm lazy and just restart the machine rather than restart BOINC or init.... really bad form I know! I'll try and be better in the future : )

---

Crunching SETI@Home as a member of the Whirlpool BOINC Teams

NEW AND IMPROVED PENGUIN SOUP!!!!
with more NI! than ever before!!!!

oh wow...
put ubuntu and 2.2b on the E6300.
wow!
fast ain't the word.
buying a round of shrubbery for Simon, Crunch3r, Hans,
Ben, Joe and Alex.

---

Bring me...a shrubbery!

Seriously though, glad you like them. Let's see whether Linux can't catch up to Windows :o) In some preliminary testing, it's even been quicker.

Regards,
Simon.

---

Donate to SETI@Home via PayPal!

Optimized SETI@Home apps + Information

Forgive me if this is obvious... It can stay an "always on" machine.

BOINC runs as a startup script for me, and sometimes I'm lazy and just restart the machine rather than restart BOINC or init.... really bad form I know! I'll try and be better in the future : )

Not necessarily bad form, if the machine is your own and not actually doing anything critical. I run boinc on several live servers and my clients would not be at all happy if the machine was down at the wrong time!

BOINC should automatically set it to 19, I've never seen it do otherwise, so I think restarting BOINC should fix it permanently.

Renice helps but only for a while, couse when boinc starts counting another task, seti client turns back to user priority. It happens on all my debian sarge machines ;)...

---

Same thing here... 2.2B science app running (blazingly fast) at nice 0 on Ubuntu 5.10.

Thanks for a great effort to all people who put time and effort into these apps. I have no doubt the same people will spend even more time and effort figuring this priority-thingy out. :)

Greetings,
Sander

---

Same thing here... 2.2B science app running (blazingly fast) at nice 0 on Ubuntu 5.10.

Thanks for a great effort to all people who put time and effort into these apps. I have no doubt the same people will spend even more time and effort figuring this priority-thingy out. :)

Greetings,
Sander

Same here: all slackware boxes behave properly, but Ubuntu one runs with 0!
It is Ubuntu problem, I would dare to say.

BR
Iztok

I sort priority thing out by installing boinc-client from backports using aptitude. To retain previous tasks just copy project catalog and .xml files.

---

Segmentation fault on all Fedora core 6

./KWSN-R2.2B-SSE2-P4
Segmentation fault
./KWSN-R2.2B-SSE
Segmentation fault
./KWSN-R2.2B-MMX
Segmentation fault


cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R) Xeon(TM) CPU 2.40GHz
stepping : 7
cpu MHz : 2379.259
cache size : 512 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
bogomips : 4762.44


version 1.3 is running good.

Segmentation fault on all Fedora core 6

[...]

version 1.3 is running good.

Just to double-check:

32-bit or 64-bit OS?

Happy crunchin',
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)