• 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.

SetiQ Questions

narzy

Elite Member
I am sure this is documented somewhere but the hell if I can find it. needs some help setting up a local Q and configuring the clients, first anything I need to do besides install and run seti Q on my Q box? what do I need to do to configure the CLI in win2k and XP to every time connect to the Q box? also how do I get linux to auto start seti when it starts up and use the setiQ?

thanks.
 
I dont know much but on the client side I'd run SETI Driver and point the proxy setting to your Q box (use the IP?)
 
For more details check out the hobbit site in my sig ,there are FAQs for SETIQ in there 🙂

Btw SETIQ won't get any WU's until the 1st client has sent in a result
 
As far as the server box is concerned SetiQ will run fine with the default settings. I would just reccommend changes to the dump time and max and min days in the cache. You can edit the client.ini and user.ini files to turn on "look for sweet WUs" and "VLAR routing" to help get the best WUs to your clients.

In setidriver just add the local ip address for your Q server and the default port is 5517 as Sukhoi said. For clients not using setidriver the sting from Sukhoi at the end of the target field of a shortcut will work.

Hobbit site
 
Queues

Pending= Currently processing WU
Waiting= Waiting to be processed
Results= Complted WU's to be sent to Berkely
History= Completed WU report
 
You can edit the client.ini and user.ini files to turn on "look for sweet WUs" and "VLAR routing" to help get the best WUs to your clients.

You can also do this via the browser 🙂
 
Back
Top