• 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 works with SetiDriver?

C

conjur

No Lifer
Sorry for a question that has probably been asked before (but this place is very slow for me from work today and some initial searching came up with nada).

Anyway, I have several machines running SetiDriver at home and I'd like to just setup my own queue at home so I don't have to worry about each machine maintaining a 10 WU cache and trying to upload WUs, etc. If I install SetiQueue on one of them, will it work with the existing SetiDriver folder/WU structure or does it have it's own to where I should let my caches deplete and start fresh with SetiQueue?

TIA!
 
You can run them both on the same machine and even have the Setidriver point to the queue on the same machine to get WUs . However, it might be cleaner to have Setiqueue in its own directory.
 
Thank you, my kindred Setians! 🙂

Oh, btw, glad to see you toughed it thru, Migroo! See you're on a quest to 2K! Crunch on!
 
Since you're planning on running your own personal Q, may I suggest connecting your Q directly to Berkeley rather than passing to another public Q - especially OK's. Just a suggestion🙂
 
I have my SetiQ directory inside my setidriver directory and it works fine. Just point all your setidrivers to the internal address of your setiq machine and it will work fine.
 
When I started up my SetiQ at home while using SetiDriver I just set the queue up on the box I wanted it on. Filled up the queue with WUs.

Then on that same box set the SetiDriver Desired Cache Size to 1 (one). In the Proxy/Socks section click Proxy Server and in the Host box put in Localhost or 127.0.0.1 . In the Port box put in 5517 if using the default or whatever port you set SetiQueue up with. Up in the top right click Auto Transmit.

Then watch your SetiDriver process the WUs until it gets to the last one. Make sure that when that box finishes the last WU that it grabs another from the SetiQueue and that it has transmitted all the results to the SetiQueue.

If that box works ok then you can go to the rest of the network and click Auto Transmit,
and Proxy Server and in Host put in the IP of the SetiQueue box or if your network works well you can use the name of that box. For the Port enter 5517 if using default or the port you set up SetiQueue with.

This is a long-winded answer but maybe there are some other people out there with the same question. I know it took me a few tries to get SetiQueue working.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top