> 1) get a job from the server > 2) download the executable > 3) anti-virus program deletes the executable > 4) job bombs out because executable missing > 5) go to 1 > > As of right now, as far as I've heard, > the client re-downloads the executable only on startup. > That's better than the above. > > It's not clear to me what the solution is, > or if we really need to do anything. > Suggestions welcome. > > -- David >
1) Not check if all files in place for projects with no work on client. It will save some bandwidth in some cases and will not do harm in others. 2) This will not solve loop situation you described indeed. Currently such loop will be reduced to 1 task per day due to quota limits. But maybe it's worth to maintain some additional failure counter inside client itself and just stop downloads after some number of "file missing" errors? Apparently user intervention required anyway to solve problem. (Unless BOINC will retaliate by deleting fool MCAffe antivirus in its own turn ;D ) _______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
