The WUs are not showing as complete because they are being sent
back to Berkeley instead of SetiGate.  You forgot to start the seti
client with the -proxy parameter pointing to the machine running
SetiGate.


--

William Dryden

No of SETI units returned: 14227
Processing time: 24 years, 285 days, 16 hours.
(Total hours: 217096)
www.setiathome.ssl.berkeley.edu

"TSN Mail" <predom@thingy.ath.cx> wrote in message
news:403ea248@news.leadingedgeinternet.net.au...

Hi, me again... In addition to this... its annoying that SetiGate

won;t

track clients that are unix/linux based. Is there a program that will

allow

me to track all types of clients if even just by IP Address?? So that

I can

monitor the performance of all the diffferent clients?

Cheers.

"TSN Mail" <predom@thingy.ath.cx> wrote in message
news:403ea1b8@news.leadingedgeinternet.net.au...

Hi all,

I;ve recently rejoined the Seti@home community, and in the past I

have

always used Seti(gui Client) with SetiGate as the cache for WUs.
Now I am using the CMDline client with Seti Spy and using SetiGate

again.

My problem is that SetiGate appears not to register completed units

from

some of the clients on my network.
The clients are getting new work units, but it is showing the old

work

units

as still processing.

Screenshot at: http://thingy.ath.cx/SetiGate001.png

Any help would be appreciated. Maybe I have setup SetiSpy wrong, or

SetiGate

is out of date? I am not sure...
Thanks.