Hi,
The client I started interactively with
--exit_when_idle
is still running, having processed several tasks.

A client started from a batch job with
--abort_jobs_on_exit --exit_when_idle --exit_after_finish
did finish after one task, but did not upload the result.

Do you know of anyone running boinc in batch jobs?

Cheers,
Rod.



David Anderson wrote:
> I think the --exit_when_idle option will do what you want.
>
> The documentation is lacking in this area.
> I'll fix this soon.
>
> -- David
>
> Rodney Walker wrote:
>   
>> Hi,
>> In order to run Boinc in a batch job, I`d like to run 1 task and then 
>> exit. The only promising command line argument is
>> --exit_after_finish
>> but this is in the debugging section - is the upload of the result done 
>> in this case?
>>
>> A really useful option would be a soft and hard limit on the time the 
>> task should take. This would allow one to fill a cluster with boinc jobs 
>> when it is idle, but free up the slots quickly when the high priority 
>> jobs arrive.
>>
>> Cheers,
>> Rod.
>>
>> Ps. Apologies if this is the wrong list, but I did not find anything 
>> more appropriate.
>>
>>     
>
> _______________________________________________
> boinc_dev mailing list
> [email protected]
> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
> To unsubscribe, visit the above URL and
> (near bottom of page) enter your email address.
>   

_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to