Subject: Re: Caching Work Units
From: "Stratcat" <none@no.org>
Date: 21/07/2004, 16:52
Newsgroups: alt.sci.seti

"Chefry" <dont.have.email@all> wrote in message
news:82qsf0hapfm3lgq0ke0kaouitqlq5hht5m@4ax.com...
On Tue, 20 Jul 2004 21:46:43 +0100, "Sonic"
<Freeflyer91@hotmail.com.NoSpam> wrote:

Google for SETI Spy or SETI Driver.

I have Seti Spy and it doesn't cache, as far as I know, but Stei Driver
looks good. I'll
try it Thanks


SetiSpy is the monitoring utility. SetiDriver is the caching utility. Either
weill work well as a stand alone, buthey work very nicely together.

If you runn 2 concurrent CLI's, there's a switch to tick on SetiDriver
called "create Setilog.csv", which it will, upon completion of the WU.
You can then add the "SetiWatch" as an additional monitoring/logging
tool. It will log all WU's completed, even if a faster WU happens to
process and complete while a slower WU is concurrently running, and
gets missed by SetiSpy.
-- Strat