Yes, APP_INIT_DATA is exactly what I was looking for. Thanks!
As for any pattern, all I can say is that it seems to happen more often with the windows OS, but that might be because the majority of users run Windows. I will reiterate, this happens very rarely. I see it about once every several days, which translates into about 1 in every 10,000 WUs. Eric From: Juha [mailto:[email protected]] Sent: Friday, May 27, 2016 9:55 AM To: Eric Driver <[email protected]> Cc: BOINC Dev Mailing List <[email protected]>; boinc_projects <[email protected]> Subject: Re: [boinc_projects] problem with check pointing On 26 May 2016 at 19:11, Eric Driver <[email protected] <mailto:[email protected]> > wrote: I've noticed that sometimes when the client starts a fresh work unit, it will read the check point file of a previous work unit. Can you tell if there's any pattern? Same host or OS or client version? One way I can fix this is to use a checkpoint filename unique to the WU (up until now all WUs use the same generic name). I'd like to key off of the work unit dat filename, but it is not immediately apparent how to get my hands on that information from inside my main app. Can someone point me to an easy way to do this, or possibly another solution to this problem. There's APP_INIT_DATA::result_name and you get APP_INIT_DATA with boinc_get_init_data(). If your app doesn't use BOINC API there's init_data.xml -> result_name. -Juha _______________________________________________ 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.
