On Sat, 10 Apr 2004 16:02:08 +0000, Beemer Biker wrote:

"My Name's Nobody" <Nobody@msn.com> wrote in message
news:gLUdc.19439$hd3.10886@nwrddc03.gnilink.net...

I just switched to linux recently (last week) and looking thru my office
email i see several warnings about the power doing down so that script I
put together may have been a problem after all. (deleting those .sah
files).

for win32 duals, the command line setiathome.exe properly loads the next
wu.  In looking at the readme for a unix system I see (doing this from
memory as I am at home) while(1)
 setiathome
 wait(20000)
loop

just guessing about the above and its syntax but I dont have to do that
for win32 command line.

should the while loop have gone in?  Whenver i run "top" I always see
the two setiathome at the top of the page with cpu0 and cpu1 so it would
appear that both are running.  I tried a -cpu 0 and it didnt like that
command switch.  I have bene running seti since early when it first came
out and have 40k + units but have never run linux till last week.  I
built an smp kernel and that kernel is running.

Beemer Biker,

Some Linux systems have a problem with the S@H client quitting for no
reason at all. That while loop tries to start it every 20,000 seconds and
fails if its already running. In that sense its harmless.
I can't say I have ever seen the problem.

The linux commands are not much different to the windows ones. In linux
CPU affinity is managed by the kernel, so the -cpu n switch has no effect.
./setiathome -h shows you all the commands, just like in windows.

Have you tried ksetispy? 
Thats SetiSpy for Linux. Last time I used it, it had WU cacheing too.

The linux client is not as fast as the winnt-cli client, except at low
angle ranges, where there is a bug in the windows client. 

Regards,

Roy Bamford
-- 

Computer users fall into two groups:-
Those that do backups
Those that have never had a hard drive fail