> Set the resource share of the backup project to be really tiny compared to > the primary project. A ratio of a million to 1 is possible, and that > would > have the backup project only doing an hour of work every century on its > own, after a few tasks to get it into the overworked state. Set your > "Connect every X" to match reality (0 if you are always connected), and > your "Extra work" to be a couple of days (long enough for most outages)l. > An overworked project (and the low resource share project in this case is > almost certainly going to be overworked) will only be asked for work if > the > total queue is < "Connect every X". > No, this will no way be the same as true "backup project" feature. With big difference in resource shares all downloaded work will immediately go into high priority and such project will always do more work when actually needed as it would be only backup project to some other project that time to time out of work. Backup project feature requested many times indeed and very useful and needed feature IMO.
_______________________________________________ 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.
