• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

setiqueue server and clients

smokey7722

Senior member
I have a few machines here, all have their own caches and all for WU's, but I want to set up setiqueue on the one machine I call the server. BUT I also want that machine to be running the client software to crank out wu's also. Anyone out there that can help me out?
 
I have a dual P-133 set up as a SetiQ server and it runs the Seti client (course it takes awhile 😀 ).
I use Seti Driver and Seti Spy on all the computers and just direct Seti Driver to my SetiQ IP. I had all of them connecting and caching independently before, so all I had to do was tell Seti Driver to use my server as a proxy. Easier to do it than explain it 😀
 
No problem at all - the SetiQueue program takes very little cpu power to run. I run such a SetiQueue at home for my "fleet" of machines, and I run an instance of the SETI client on each of the CPUs(dual-config) as well.

I simply gave the machine that is the SetiQueue "server" a static IP and run the queue - in my case, it's a private IP: 192.168.1.40:5517 Then on the regular SETI clients running on each CPU, I simply use the -proxy command to point them to the SetiQueue(as above) and that's it.

I don't happen to use SetiDriver on any of my PCs, but it's still fairly easy to setup. 🙂
 
So for the server, when I put the client on it, do i use a loopback ip, 127.0.0.1 or do i use the actual IP, which in my case is 10.0.0.2.
 
I use the loopback 127.0.0.1 on one Q and the name localhost which is the same as 127.0.0.1 on another. That's what happens when you do stuff late at night🙂

Both have been working fine for months.🙂

Interesting concept using the computers actual IP addy.😕
 
<I have a dual P-133 set up as a SetiQ server and it runs the Seti client (course it takes awhile >

I have a dual PPro180@200 256K cache running my home SETIQ, as well as the SETI client, and it does take awhile for the client to finish. 🙂 Maybe I'll look around for some matched PPro 200s with 1M cache to see if I can squeeze a bit more out of it. 😉😉

And I use the PC's IP address in the client. Works just fine. 🙂
 
Thanks to all, I now have it setiqueue running on my server and have been dropping results one by one back to berkeley. I have another 20 or so results to send in, stupid dialup!
 
Back
Top