Attila: I checked in a fix for this. If you can, build the client out of trunk and see if it works. -- David
On 19-Jul-2010 9:16 AM, attila csaba marosi wrote: > Hello, > > I am trying to use the "--abort_jobs_on_exit" parameter (on linux32, boinc > client 6.10.56): > > boincworker45:~# /usr/local/boinc-6.10.56/boinc --sched_retry_delay_min 60 > --sched_retry_delay_max 120 --abort_jobs_on_exit > > ... > 19-Jul-2010 16:04:16 [cloud] Computation for task wu_00060_0 finished > 19-Jul-2010 16:04:17 [---] Received signal 2 > 19-Jul-2010 16:04:18 [---] Exit requested; starting abort sequence > 19-Jul-2010 16:04:21 [cloud] Sending scheduler request: Requested by user. > 19-Jul-2010 16:04:21 [cloud] Reporting 1 completed tasks, requesting new > tasks > 19-Jul-2010 16:04:23 [cloud] Scheduler request completed: got 1 new tasks > 19-Jul-2010 16:04:23 [---] Abort sequence done; exiting > boincworker45:~# > > > It is always requesting new tasks after abort, before exit. Is it supposed > to work like this ? (It is "trading" one result for another one.) > > > Thanks, > Attila > > > --------------------------------------------------------- > MTA SZTAKI Computer and Automation > Research Institute, > Hungarian Academy of Sciences > --------------------------------------------------------- > _______________________________________________ > 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.
