Yes, BUT, if it finishes a work unit and cannot get the server to take the result AND send a new work unit, it is my belief that it will terminate. Then, it will need to be restarted. It would be nice if there was some sort of 'binary exponential backoff' built in like Ethernet has, to keep the server from being swamped when it first comes back up. Failing that, they hope people will more-or-less even out the distribution of cron start-times.On Thu, 22 Apr 2004 09:45:39 -0600, "Rodolfo J. Paiz" <rpaiz@xxxxxxxxxxxxxx> wrote:
At 09:12 4/22/2004, you wrote:
Why? On fast machines, returning results every four or five hours, there is significant time lost waiting two hours for the next run.
Setihome does not terminate after finishing one workunit, As soon as setihome
finishes a set, it uploads the result, downloads another set, and goes right
to work on it. There's no waiting for the next run. On the other hand,
there's no harm in running it twice an hour because the mutex will prevent
multiple instances from running. --
Steve
-- Fritz Whittington Before you criticize someone, walk a mile in their shoes ... That way when you do criticize them, you're a mile away and you have their shoes!
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
