New to TA

AlricTheMad

Member
Jun 25, 2001
125
0
0
Ok folks, I have 2 PC's cracking WU for Seti@Home.

1 CLI running on a 700mhz duron w/ 256 MBor sdram
1 CLI running on a Athlon XP1600 w/ 512MB RAM On Linux & Wine

I was running WU's at about 4.5 hrs on the XP but now my times are diluted by the Windoze machine.

Anyone know how I can determine run time for the Linux box alone?

Also who can we petition to recompile the unix CLI with the Intel compiler?

Gotta be faster to run it native in Linux than under Wine.

I hope to hit the 75% mark in a month or 2. Sine I now have 15 WU's since I really started on Jan 16 anyone knpw if this is possible?


AlricTheMad
 

KCjeeper

Senior member
Sep 29, 2000
210
0
0
Welcome to the TeAm, Alric!!!

You can set SETI Driver to create a log, and then view it with a spreadsheet. That will help you keep the machines seperate.

Sorry, don't know the answers to your linux ??'s...I have tried 3 different distro's, and haven't got even one to work on my macines, let alone run SETI.
 

Poof

Diamond Member
Jul 27, 2000
4,305
0
0
Anyone know how I can determine run time for the Linux box alone?

Well, you can always do a -stop_after_process (or equivalent) as a parameter on the seti executable (or place, ie., "touch" a file by that name in the directory), and then take a look at the results file before manually uploading it yourself, to get the processing time (which will be in seconds - just divide by 3600). Alternately, if you had a windoze box with Setiqueue on it, even though both machines would be crediting your account, the 2 machines would have separate stats entries listing the WU times. Along that line, you could try flushing that one machine through OK's or one of the other TeAm queues to get that separate listing.

Also who can we petition to recompile the unix CLI with the Intel compiler?

Many of the SETI principals (eg., Eric Korpela, Matt Lebofsky, etc) monitor and post on the alt.sci.seti news group. You could maybe start a thread and encourage people to keep posting in it. It's a PITA to get them to change stuff in general. I know because I have a 3.03 alpha linux client with a *known* bug (it doesn't write the lock.sah file correctly and thus there's an issue with trying to get the client started and/or running it with other parameters other than the -nolock one... :()

I hope to hit the 75% mark in a month or 2. Sine I now have 15 WU's since I really started on Jan 16 anyone knpw if this is possible?

My sparc IPX is at 75.842% with 40 WUs (@ 16 days/WU... LOL). You'll probably hit it very easily in that time with your rigs. :)




 

Crazee

Elite Member
Nov 20, 2001
5,736
0
76
Welcome AlricTheMad! :D

Its great to have you here! :D :D :D

Sincerely,


CrazeeTheNef ;)
 

Logix

Diamond Member
Jul 26, 2001
3,627
0
0
Welcome to the TeAm! :D

If you want stats, you can have your client run through OK's proxy server, and you'll get a page that looks like this: Link
 

ProviaFan

Lifer
Mar 17, 2001
14,993
1
0
I run the cli seti for linux on my Redhat 7.2 box natively and have no problems with it. What is all this fuss with wine (yeah I know what wine is, but don't know why you'd want to run seti through it)?
Anyway, let me suggest that if the machines you have are networked, run SetiQ on one of them and then set up both of them to flush throught it. That will give you detailed stats on each PC (that's what I do). Or, you could flush through OrangeKid's proxy, but he has occasional downtimes.
 

AlricTheMad

Member
Jun 25, 2001
125
0
0
Ok How do I start using OK's proxy. I didn't see any info on the home page.

Are the instructions in the Help thread?

If So I will be checking there later.

Thanks for the warm welcome!!!

Alric
 

Poof

Diamond Member
Jul 27, 2000
4,305
0
0
jliechty -
I run the cli seti for linux on my Redhat 7.2 box natively and have no problems with it. What is all this fuss with wine (yeah I know what wine is, but don't know why you'd want to run seti through it)?

No problems with the linux client... But the fuss is the fact that because the linux client is unfortunately slower than the CLI (due to the what it was compiled with), some feel that the time saved to pump out more WUs on a more stable OS with WINE is worth it! :D

Alric - to use OK's queue, just run SETI to point to his machine using the "-proxy" parameter. Ie:

./setiathome -proxy orangekid.teamanandtech.com:5001
 

Shuxclams

Diamond Member
Oct 10, 1999
9,286
15
81
./setiathome -proxy orangekid.teamanandtech.com:5001 &

You could even renice it -nice -19 :D










SHUX
 

IndyJaws

Golden Member
Nov 24, 2000
1,931
1
81


<< Oh yeah, I forgot... And welcome to the TeAm (why we spell it that way I have no idea, but...) :D >>



Cap T and A (heh heh heh...he said T&A ;) ), come from Team AnandTech. Clever, eh? :)
 

Jerboy

Banned
Oct 27, 2001
5,190
0
0


<< Ok folks, I have 2 PC's cracking WU for Seti@Home.

1 CLI running on a 700mhz duron w/ 256 MBor sdram
1 CLI running on a Athlon XP1600 w/ 512MB RAM On Linux & Wine

I was running WU's at about 4.5 hrs on the XP but now my times are diluted by the Windoze machine.
>>



Thats not any better than my OC'ed TB then.

I'm getting 4:20 to 4:30 (H:MM) on my TB @1485MHz running Windoze Me and 512MB DDR.