On Sep 28, 2009, at 2:05 PM, David Anderson wrote: > I'm not sure this will solve the problem. > Seems to me the client will go into this loop: > > 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.
The case you outline *I* don't see as a problem in that after a couple cycles I should be able to notify the project and / or stop running the project or sub-project. The first case is the problem because in this case the executable is downloaded and it is not needed and with NNT could wait until such time as I set to allow work when the current up to date exe would be DL. Bottom line, don't download if found missing on start up ... wait until there is need, detect missing file and get it then where it may or may not be deleted... My original point was that I was surprised that BINC is downloading exe files for projects for which I will not be running work for another month ... and I still don't know why it has to download a missing file when I have no work for it on start up ... _______________________________________________ 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.
