seti service script - proper run level (still problems)

[Fritz Whittington]

On or about 2004-04-22 10:54, Steven Stern whipped out a trusty #2 
pencil and scribbled:

>On Thu, 22 Apr 2004 09:45:39 -0600, "Rodolfo J. Paiz" <rpaiz at simpaticus.com>
>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
>  
>
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. 

-- 
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!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3497 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20040422/9144c153/attachment-0001.bin>