A few setiQ questions.

[blade47]

I have just setup the newest version of setiq a couple of days ago and had some questions about what a few of the settings do.


Consolidate clients (I believe this is is under the user settings when logged in as admin)?

Permanent Client (only available as admin as well I think)?

I have no idea what either of those do so if anyone could explain it would be greatly appreciated.



I know what 3.03 VLAR Routing does I'm just not sure which clients are affected by the slow buggers. Is it only the windows cmd line version that has problems with them? Is the windows gui version quicker with those particular wu's than the cmnd line version (I know at one time it was). If so then I am assuming I could install the gui version of seti on 1 machine and let it handle all of the VLAR ones so as to not bog down my cmnd line clients.


The machine I am running setiq on right now doesn't seem to be caching wu's for it's seti client. If I am not mistaken it's just doing a pass through and getting it's wu's directly from seti. I know for the old versions of setiq you had to patch the client to get it to work properly. Is this still the case? If so where can I find some info on how to do this (it's been a long time since I did it). If a patch is required would it be possible to just run setidriver on the setiQ machine and point it towards the Que instead of bothering with a patch.

Hehe sorry for all the questions but I've been out of the loop for quite some time now.

 

[Engineer]

Not sure about the "Consolidate Clients", although I would guess it merges all clients of the same user into one....i.e. if a user has multiple PC's with different IP's using one Queue, that Queue will merge all the clients for that particular participant into one..but not sure.

The Permanent Client is set to on if you want to keep someone active in your queue, even if they haven't submitted a WU for a very long time. This is to keep the Queue from deleting that client after so many days of inactivity. Again, someone else may shed a little more detailed light on this one too

Good luck....

 

[Baldy18]

The VLAR Routing option will keep VLARs away from Windows 95 (95/98/ME) based clients. It will instead route them to nonwindows clients or windows NT based clients (Windows NT/2K/XP). It is only the Windows 95 based slients that take a real bad hit from VLARs althoughm others so also it is minimal. GUI won't help do VLARs anyfaster and will slow down all the regular ones.

 

[Assimilator1]

AFAIK the GUI client does do VLAR WU's faster than the CLI but depsite this the CLi is still faster overall

Blade 47
Good to see you back in the loop
I don't believe the VLAR routing can distinguish between the GUI & CLi clients of SETI

You don't need to patch SETIQ anymore ,that was for the old text version!:Q ,........wow I didnt realise you had been out of the loop that long!

When you connect a new client to SETIQ it has to 'pass through' to get the user_info for it ,if you find that it grabs more than 1 WU for it from Berkley disconnect & restart the Q.The client should then grab WU's already stored.

Btw you have put SETIQ's proxy add in the commandline for SETI havent you?

 

[blade47]

Thanks, looks like it's time to play around with some settings.


Assim1, I have been out for quite some time. I had setup the first gui version of setiQ (though I never explored all of the settings and such) then pretty much stopped checking on things though I did leave it running up until a few months ago (I think it was) when I sold the system that I used to run setiQ on.

I have since bought an athlon xp system and figured it was time to see what it could do.

BTW I have added the proxy settings to my clients. I'll just have to keep a closer eye on my Q machine to check for sure if it is getting the wu from the setiq or berkley.

 

[Assimilator1]

Yeah going by your stats at Soni's site you were still producing until February
Stats seem to be down atm for me ,though it could be down to NTL(my ISP) messing around again:|

BTw Nexus9' stats went down ages ago ,late last year ,he more recently mentioned that he might do another site for TA for 1 of the other projects

 

[blade47]

Yeah I noticed the nexus9 stats had gone down, that was always my favorite. Guess I'll update my sig.

 

[Rattledagger]

"3.03 VLAR Routing - The default is None. If set to "Avoid win-cmdline" when SetiQueue downloads a VLAR workunit from the seti@home server for this user for a 3.03 revision win-cmdline queue, it will route it to any other 3.03 queue for the user that's not already at 150% capacity. (picking the one that needs to the most or least depending on how you look at it). This feature is present because the Windows cmd-line client is particular inefficient at processing VLAR workunits then other clients. A VLAR WorkUnit is one with an Angle Range of less then 0.15."

Since SetiQueue makes independent queues for gui and cmd-version, you've got VLAR-routing here.
On the other hand, I don't know if SetiQueue makes independent queues based on win9x and NT, but since both is 3.03-win-cmd I can't see any routing away from 3.03-win-cmd here.

"Permanent client - By default SetiQueue will automatically remove any client that has been idle for longer then the configure Obsolete Time. If this value is set SetiQueue will not age out this client."

To make sure SetiQueue doesn't delete a queue, make one of its clients permanent.

As for "consolidate clients", I've no clue.

 

[Robor]

Originally posted by: blade_47
Yeah I noticed the nexus9 stats had gone down, that was always my favorite. Guess I'll update my sig.

Nexus9's stats are down? /me goes to look...

EDIT: Oh, I forgot about that. I looked in my sig and I already removed Nexus9's site. Yes, I posted just so I could see my sig. Call me lazy or call it a nef.

 

[Assimilator1]

Thanks Rattledagger for the info ,I think we need clarifcation from Ken as to whether SETIQ routes according to OS as well.

 

[blade47]

Thanks Rattledagger

LOL @ Robor

I finally got seti installed on my smoothie (linux gateway) so now I know I can definetly use vlar routing though the box is only a P2 @ 350 mhz.