There's some discussion of this in "A first attempt to fix the bug where apps die with exit(1)"
http://boinc.berkeley.edu/trac/changeset/7f6ab8d49eeaa6df58bf3bc4f61f2f7540d2c7e7/boinc >________________________________ > From: Josef W. Segur <[email protected]> >To: [email protected] >Sent: Friday, 8 March 2013, 6:39 >Subject: Re: [boinc_dev] 194 (0xc2) EXIT_ABORTED_BY_CLIENT > >On Fri, 08 Mar 2013 00:10:45 -0500, Raistmer the Sorcerer <[email protected]> >wrote: > >> Under what condition client can abort task with such error value ? >> > >Fleshing out Raistmer's question, it's related to this post: > >http://setiathome.berkeley.edu/forum_thread.php?id=70742&postid=1343946 > >In all three cases, the science application had completed and called >boinc_finish, but was restarted from the last checkpoint and killed with that >error sometime later. Both hosts on which it was seen were running BOINC >7.0.52. > _______________________________________________ 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.
