On Friday 27 August 2004 7:47 pm, Randall R Schulz wrote:
Peter,
On Friday 27 August 2004 17:31, Peter B Van Campen wrote:
...
Hi Guys,
I've a similar prob on SUSE 9.1 Pro. SETI has run ok for me since ver 8.0 I have run KSetiwatch for a long time as well. I now use KSetiwatch 2.6.1.Starting w SUSE 9.1 KSetiwatch shows a stopped client when ever the system is restarted. It feels like a permissions problem. If I open a Konsole I cannot start (./setiathome) the client, even tho it is in a sub dir of MY users home dir. But if I su and start the client then it all takes off and goes great. I asked heve on the list and no one offered any suggestions.
I should have mentioned that I originally used KSetiWatch and found that there's some kind of problem (a race condition, perhaps) in which the SETI@home client stalls. For some reason, KSetWatch always showed 70% complete when this happens and "ps" output suggests that client is sleeping (not stopped, e.g.). Stopping and restarting it gets things going, but often this happens when no one is around to notice, resulting in wasted CPU cycles.
So far, this has not happened over the past week or so of running with KSetiSpy, and it typically happened about once every day with KSetiWatch.
SUSE 9.1 does not have KSetispy, is it a replacement for KSetiwatch that also has WU caching, or is it usable along side KSetiwatch? Where might it be found?
True, SuSE 9.1 does not bundle KSetiSpy. These days, my favorite place (my first stop, anyway) for finding RPMs is http://rpm.pbone.net/. Its index of available RPMs seems to be the most extensive I've yet found (though at the moment it's letting me down totall--i.e., it's not responding).
And yes, as I mentioned, KSetiSpy has its own WU download and caching feature (though it uses the stock client to do so).
I don't think it would play well with KSetiWatch--they both perform similar functions and would almost certainly interfere with each other.
Thanks! .............. PeterB
Randall Schulz
Hi Guys, Until you mentioned it I never considered that KSetiwatch could be the problem. I've been running the seti client from command prompt for several hours now with no problem. I will look for KSetiSpy and give it a whirl. Not sure what the problem is with KSetiwatch in suse 9.1. I am running it under 8.2 with no problems at all. Many thanks for the tip. Jim Flanagan