On Friday 27 August 2004 5:33 pm, Jeffrey L. Taylor wrote:

Quoting linuxjim :

...

Hi,

I'm running a seti client which runs data sets, but I can't seem to keep it running. After one, or a few data sets run, it stops processing more sets. It looks like it finishes a set, but does not start another one. Any suggestions welcome. I'm runing suse 9.1 with KDE. I'm running the seti version "i686-pc-linux-gnu". This box is an Athlon 2500 cpu on an abit AF7 board.

Jim Flanagan

The SETI server is often unreachable. Sometimes for days. Just leave it running. If it doesn't start another packet in a week, then worry.

Jeffrey

Hi Jeffery, Understand your point, but I don't seem to have this problem on other machines. Running on a much slower box under suse 8.2, and several win boxes this does not seem to happen. Not sure why. Jim Flanagan

On Friday 27 August 2004 17:52, Randall R Schulz wrote:

Jim,

On Friday 27 August 2004 15:24, linuxjim wrote:

...

Hi,

I'm running a seti client which runs data sets, but I can't seem to

KSetiSpy has a very nice GUI that will show you everything you want to know about your work unit and the history of processing at your site. It can manage multiple accounts, too, assuming they're all accessible from the system on which its running.

...

Jim Flanagan Randall Schulz

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. 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? Thanks! .............. PeterB

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

Jim, On Saturday 28 August 2004 06:27, linuxjim wrote:

...

I now have KSetiSpy up and running. Sourceforge.net has an RPM for suse 9.1. Installed no problem and even set up an item on the menu.

One thing I can't find is with Ksetiwatch I could see then number of data sets the local machine has completed. I KSetiSpy is shows the total user stats, but I can't find the number of units this client has run. Is there a way to see this?

On the "Results" page, there's a button labelled "View Log" which will show the log of results returned locally. But to be honest, I haven't quite got the required setup ("Setup" page, "Loggin" tab) done correctly and my log is empty. I find both the GUI and the documentation confusing about where a file name vs. a directory name is required and when you must create the necessary file system entity yourself. I got the caching mechanism to work by trial and error (and by reading the handbook., of course) Good luck.

Thanks,

Jim Flanagan

Randall Schulz