El Jue 30 Abr 2009 13:45:38 Martin escribió: > Then that is an Achilles heel for gaining feedback on what was accepted > by the client... > > Apache can report what URL downloaded whatever, so that is one means of > feedback for servers under direct project control. > > Another means could be that that the next client request also lists what > was accepted last time. Rather messy and that would leave unaccepted WUs > in limbo for too long. > > And then there is the even more messy WU abort... > > Soooo... > > At present, how do the download servers know to delete > downloaded/expired WUs if they can't 'phone home'?
That depends on the project. If it's the same server, file_deleter deletes download files from the local 'download' directory. If it's a different server on the LAN, usually it's NFS-mounted, so file_deleter also issues a normal file delete. BURP sends a request to mirror servers to tell them the file should be deleted. It's a completely custom request, and probably triggered by the mirror system, not the file deleter. I don't know what einst...@home does for its geo-distributed download servers. > What is done at present about WU failed downloads? Nothing that involves the download servers. _______________________________________________ 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.
