Tweet
Setiqueue-guide 1.50 Beta.
Since the new setiqueue is out of beta, it's time to update the guide too.
First, if you haven't got SetiQueue, the download is here:
http://www.reneris.com/seti/default.asp
-- Setiqueue-guide, ver. 1.50 beta--
Index:
Introduction;
Installation & initial configuration of SetiQueue:
Running SetiQueue & more configuration.
Configuration of the seti@home-clients;
Automatic execution of SetiQueue;
Known errors;
Other info;
Introduction:
-------------
For people don't knowing, SetiQueue (Setiq for short) is a cache-program that runs as a seti-proxy on a machine. Its main use is for machines in network, but can also be used on a stand-alone-machine. The SetiQ-program is win32, and must be run on win9x or NT, but it can cache units for all form of machines connected to your machine. The new Setiq can work with multiple seti@home-users, and is a win32-gui-program. The old Setiqueue was a cmd-version. Most commands, status, configuration is done with your web-browser.
Installation & initial configuration of SetiQueue:
---------------------------------------
First, download setiq and install/unzip it to its own directory. Don't run seti@home in the same directory, since this can lead to problems. If you've run the old cmd-version of SetiQueue, don't install the new to the same directory.
Then installed, start Setiqueue with running setiqueue.exe
The default for this version is to use port 5517 for communication with seti@home-clients. If you wants to use another port, edit "Port number" under "Settings"/"Queue Server". You can also change the IP address/subnet mask; This should be the same as the machine you're running setiq on, or all zero.
The important thing to configure is to open "Settings"/"Http Server" and type a "Administration password"
After giving the client a password, all configuration except port number, ip address & subnet mask of the setiqueue-machine can be done with your web-browser.
On NT, it's a great idea to install SetiQueue as a service. To do this, first close down setiqueue. Run setiqueue.exe -i. Open "services" under "control panel"/"administrative tools" Edit SetiQueue to start as "automatic". You can now start the service.
If you later wants to uninstall the service, run setiqueue.exe -u
Note, since setiq has it's own service-installation, you can't use FireDaemon or other programs to run setiq as a service.
Running SetiQueue & more configuration.
----------------------------------------
If setiqueue isn't running, start it, either with setiqueue.exe or start the service on NT.
If running as gui, you can configure some of the things here.
If you're running as service, you must open your web-browser.
Either way, to configure in web-browser, open your browser and type in:
http://xxx:nnn
There xxx is either the ip-number or machine-name of the machine running setiqueue; nnn is the port-number, default 5517.
Hit Login (under Admin), enter the password, and hit enter.
The default should most likely work for most, but the following should probably be edited:
The default is setiqueue uses the same proxy-settings as internet explorer (WinINetDefault). If you need other proxy-settings, edit this under settings/queue server (gui) or Settings [Queue processing settings] (web).
On the same page, you can set then setiq tries to connect to seti@home-server. Before you've filled up your queues for the first time, leave "override time for empty queues" on.
"Report stats to SetiQueue server" can be disabled.
"Inter-WU download gap" is the time between starting downloading of a wu and start of the next wu. Can be set at 0.
"Inter-WU VLAR gap" (web) is as above, but should be larger than the above to minimise the possibility of many VLAR-wu downloaded in sequence.
"Look for sweet WUs" (web) if enabled, after High angle-range wu next wu immediately downloaded.
Under Settings/General there's this things:
"Email address" Only for NT5 (win2k) or later; sends e-mail here if problems with setiqueue.
"Max Queue Depth"; how many days you should queue. Max 14.
"Obsolete Clients after xxx days of inactivity"; If no client has connected a queue for getting wu/upload result, this queue is removed. Max 99; Recommend at least 7.
Most other configurations is on a queue-for-queue-basis, and must therefore be configured after you've initialised the queues.
Note, setiq doesn't start caching of a queue before first request to get wu is received from a seti@home-client.
To manually connect, hit connect and select a time. The time is how long setiq is allowed to connect to the server. If it's done before the time is up, it will of course disconnect, but will connect again if result/wu is requested before the time is out.
Configuration of the seti@home-clients:
---------------------------------------
Then setiq is up and running the seti@home-clients is pointed to the setiq-machine:
For cli, start them with seti@home.exe -proxy xxx:nnn (+ more start-switches...)
For gui, edit the proxy-part to xxx, and the port to nnn.
xxx depends on your setup, and corresponds to the machine running SetiQ.
Use either ip-address or machine-name.
nnn is the port setiqueue is using, default 5517.
Advanced client-configuration, Multi-client & Multi-user-usage:
--------------------------------------------
The new SetiQueue makes independent Queues for every seti@home-user & seti@home-client.
Most configuration is already discussed, but a couple of things is this:
under Queues:
"Enable Processing"; if disabled, doesn't download more wu from seti@home.
"Override Min/Max"; override cache-depth.
under Clients:
"Display name"; shows this instead of computer-name/ip-address.
"Permanent client"; if enabled, don't remove the client even after "xxx days of inactivity"
"Fixed IP Address"; if problems to keep machine/client paired up.
"Dedicate client port"; Can use a different port than the normal for this client.
under Users:
"3.03 VLAR Routing"; if enabled, tries to route VLAR-wu away from win-cmd. Note, for this to work, the same user must run two different clients. I think it also works if using both NT&win9x. In the latter case, NT should get the VLAR.
Automatic execution of SetiQueue:
---------------------------------
On NT, install&configure as service (see above).
On win9x, use shortcut in startup-folder.
On all NT-machines you should also install all seti@home-clients as services. The gui can't be installed as service.
Since running seti@home as service cuts off some crunch-time this is a good reason to run setiq also on stand-alone machines.
Running as service don't work with the batch-file-method.
Known errors:
-------------
Multi-clients:
The same seti@home-user can't run two different clients on the same machine. Example, he can't run both win-cmd & win-gui. If this is the only machine he's running on, the next client connecting to setiqueue deletes the queue for the other client. If dual-booting, it will probably not be detected as same machine and therefore work.
Dial-up-connection, not always connected;
I don't know with other OS, but at least in win2k seti@home has a tendency to want to dial out then done with wu, leading to problems.
Solution: Run the seti@home-client as a user that DON'T have a dial-up-connection configured.
Other info;
-----------
SetiQueue also shows statistics over done wu, how efficient different clients has been and more.
Then giving a wu to a client, the wu is marked as "pending". The status of the progress is using this colours:
Green; below average cpu-time for client;
Yellow; above average cpu-time, but below average run-time.
Red; above average run-time; the client is using longer time than expected.
Pink; status unknown, since no wu done yet.
Under Tools, you can recycle/delete all pending wu. You can move wu to another queue.
-- End ver 1.50 beta--
Comments, errors, other important info?
First, if you haven't got SetiQueue, the download is here:
http://www.reneris.com/seti/default.asp
-- Setiqueue-guide, ver. 1.50 beta--
Index:
Introduction;
Installation & initial configuration of SetiQueue:
Running SetiQueue & more configuration.
Configuration of the seti@home-clients;
Automatic execution of SetiQueue;
Known errors;
Other info;
Introduction:
-------------
For people don't knowing, SetiQueue (Setiq for short) is a cache-program that runs as a seti-proxy on a machine. Its main use is for machines in network, but can also be used on a stand-alone-machine. The SetiQ-program is win32, and must be run on win9x or NT, but it can cache units for all form of machines connected to your machine. The new Setiq can work with multiple seti@home-users, and is a win32-gui-program. The old Setiqueue was a cmd-version. Most commands, status, configuration is done with your web-browser.
Installation & initial configuration of SetiQueue:
---------------------------------------
First, download setiq and install/unzip it to its own directory. Don't run seti@home in the same directory, since this can lead to problems. If you've run the old cmd-version of SetiQueue, don't install the new to the same directory.
Then installed, start Setiqueue with running setiqueue.exe
The default for this version is to use port 5517 for communication with seti@home-clients. If you wants to use another port, edit "Port number" under "Settings"/"Queue Server". You can also change the IP address/subnet mask; This should be the same as the machine you're running setiq on, or all zero.
The important thing to configure is to open "Settings"/"Http Server" and type a "Administration password"
After giving the client a password, all configuration except port number, ip address & subnet mask of the setiqueue-machine can be done with your web-browser.
On NT, it's a great idea to install SetiQueue as a service. To do this, first close down setiqueue. Run setiqueue.exe -i. Open "services" under "control panel"/"administrative tools" Edit SetiQueue to start as "automatic". You can now start the service.
If you later wants to uninstall the service, run setiqueue.exe -u
Note, since setiq has it's own service-installation, you can't use FireDaemon or other programs to run setiq as a service.
Running SetiQueue & more configuration.
----------------------------------------
If setiqueue isn't running, start it, either with setiqueue.exe or start the service on NT.
If running as gui, you can configure some of the things here.
If you're running as service, you must open your web-browser.
Either way, to configure in web-browser, open your browser and type in:
http://xxx:nnn
There xxx is either the ip-number or machine-name of the machine running setiqueue; nnn is the port-number, default 5517.
Hit Login (under Admin), enter the password, and hit enter.
The default should most likely work for most, but the following should probably be edited:
The default is setiqueue uses the same proxy-settings as internet explorer (WinINetDefault). If you need other proxy-settings, edit this under settings/queue server (gui) or Settings [Queue processing settings] (web).
On the same page, you can set then setiq tries to connect to seti@home-server. Before you've filled up your queues for the first time, leave "override time for empty queues" on.
"Report stats to SetiQueue server" can be disabled.
"Inter-WU download gap" is the time between starting downloading of a wu and start of the next wu. Can be set at 0.
"Inter-WU VLAR gap" (web) is as above, but should be larger than the above to minimise the possibility of many VLAR-wu downloaded in sequence.
"Look for sweet WUs" (web) if enabled, after High angle-range wu next wu immediately downloaded.
Under Settings/General there's this things:
"Email address" Only for NT5 (win2k) or later; sends e-mail here if problems with setiqueue.
"Max Queue Depth"; how many days you should queue. Max 14.
"Obsolete Clients after xxx days of inactivity"; If no client has connected a queue for getting wu/upload result, this queue is removed. Max 99; Recommend at least 7.
Most other configurations is on a queue-for-queue-basis, and must therefore be configured after you've initialised the queues.
Note, setiq doesn't start caching of a queue before first request to get wu is received from a seti@home-client.
To manually connect, hit connect and select a time. The time is how long setiq is allowed to connect to the server. If it's done before the time is up, it will of course disconnect, but will connect again if result/wu is requested before the time is out.
Configuration of the seti@home-clients:
---------------------------------------
Then setiq is up and running the seti@home-clients is pointed to the setiq-machine:
For cli, start them with seti@home.exe -proxy xxx:nnn (+ more start-switches...)
For gui, edit the proxy-part to xxx, and the port to nnn.
xxx depends on your setup, and corresponds to the machine running SetiQ.
Use either ip-address or machine-name.
nnn is the port setiqueue is using, default 5517.
Advanced client-configuration, Multi-client & Multi-user-usage:
--------------------------------------------
The new SetiQueue makes independent Queues for every seti@home-user & seti@home-client.
Most configuration is already discussed, but a couple of things is this:
under Queues:
"Enable Processing"; if disabled, doesn't download more wu from seti@home.
"Override Min/Max"; override cache-depth.
under Clients:
"Display name"; shows this instead of computer-name/ip-address.
"Permanent client"; if enabled, don't remove the client even after "xxx days of inactivity"
"Fixed IP Address"; if problems to keep machine/client paired up.
"Dedicate client port"; Can use a different port than the normal for this client.
under Users:
"3.03 VLAR Routing"; if enabled, tries to route VLAR-wu away from win-cmd. Note, for this to work, the same user must run two different clients. I think it also works if using both NT&win9x. In the latter case, NT should get the VLAR.
Automatic execution of SetiQueue:
---------------------------------
On NT, install&configure as service (see above).
On win9x, use shortcut in startup-folder.
On all NT-machines you should also install all seti@home-clients as services. The gui can't be installed as service.
Since running seti@home as service cuts off some crunch-time this is a good reason to run setiq also on stand-alone machines.
Running as service don't work with the batch-file-method.
Known errors:
-------------
Multi-clients:
The same seti@home-user can't run two different clients on the same machine. Example, he can't run both win-cmd & win-gui. If this is the only machine he's running on, the next client connecting to setiqueue deletes the queue for the other client. If dual-booting, it will probably not be detected as same machine and therefore work.
Dial-up-connection, not always connected;
I don't know with other OS, but at least in win2k seti@home has a tendency to want to dial out then done with wu, leading to problems.
Solution: Run the seti@home-client as a user that DON'T have a dial-up-connection configured.
Other info;
-----------
SetiQueue also shows statistics over done wu, how efficient different clients has been and more.
Then giving a wu to a client, the wu is marked as "pending". The status of the progress is using this colours:
Green; below average cpu-time for client;
Yellow; above average cpu-time, but below average run-time.
Red; above average run-time; the client is using longer time than expected.
Pink; status unknown, since no wu done yet.
Under Tools, you can recycle/delete all pending wu. You can move wu to another queue.
-- End ver 1.50 beta--
Comments, errors, other important info?
Comment