This morning I distributed my build version to someone who had problems with fetching work from milky...@home. Before, with the 6.6.36 client he would get messages alike "Message from server: (won't finish in time) BOINC runs 71.3% of time, computation enabled 98.2% of that" ..
He only updated to use my boinc.exe and boinc.dll and restarted BOINC, which immediately and without delay went to request work from Milkyway and got it. I am running the same build on one machine that had similar problems at another project (DrugDiscovery). For the time being I returned to using the old code at my second machine to catch the Malaria log, now that Nicolas (Maire) set the correct line in the scheduler log. Not so much because we don't know if this code will continue working OK, but more to see what the log will be on a client doing such a request. It takes a couple of request before it gives the error, though and at that time there must be work available to distribute. But all in all, it would seem that the new code fixed things for now. Thumbs (and other digits) up. We could use a new alpha client with this code, so more people would be happy (and not returning to older in other ways broken 6.4 and 6.6 clients). On Sat, Jul 18, 2009 at 5:45 PM, Jorden van der Elst<[email protected]> wrote: > I've built this version from source and will go test it at Malaria, > since one of my machines is again complaining it can't get work there > due to the percentages being too much. Should I wait for Nicholas > Maire to capture the log first, is that still necessary you think? > > As else I'll switch the affected machine over to this client and will > just test-run it. > > -- > -- Jord. > -- -- Jord. _______________________________________________ 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.
