Martin 53N 1W wrote:

Eric wrote:
[...]

Nope, not on boinc. Havnt looked at it but from what i heard I'm
wondering if you can be sure its really running seti? or maybe making
profits for some drug company? how can you be sure? BTW: only the
paranoid survive...

Take a look at the project websites and check in the forums and this
newsgroup. If you are /really/ paranoid, please check the source code
also. The more eyes on the code, the better for all.

Also take a look on:
http://distributedcomputing.info/index.html

Now back to our regularly scheduled question:
The trouble is that the KSetispy program only starts one instance and
thats it. There seems to be no place in the configuration to say
"keep 2 instances running"...

Check what version you have in the RPM against the latest on sourceforge.

Myself, I had a quick look at ksetispy and saw that it offered no more
than what I was already running with Linux-Wine-SetiQueue-SetiSpy-s@h.
That combination also gave the best times due to good OS and good s@h
compile (Windows) options.


My best suggestion is to move over to boinc-s@h. The boinc manager will
correctly manage multiple instances and a WU cache automatically. If you
check in the forums, there's also a lot of work being done on optimising
the clients. See:
Linux:
http://setiweb.ssl.berkeley.edu/forum_thread.php?id=13068
Windows:
http://setiweb.ssl.berkeley.edu/forum_thread.php?id=14378

(If you want to stay with s@h only, then only attach to the s@h project.
The best for science is to look at at least one other project to share
resource with.)

Good luck,
Martin

Since i'm having trouble with the ksetispy, I'll try out boinc.
Eric