rickoic
10-12-02, 03:53 PM
I had the client.cfg file go bad on a computer, and two wu's were sent into never never land (or at least were credited elsewhere).
The file is read by the core program to get the information of client, team, and number of completed units. It then increases the completed units and rewrites the information back to disk.
In order to keep this from happening again I made the file a read only file on two different computers that were about to complete a wu. Both computers finished their wu and transmitted it, requested a new wu and gave the number of completed wu's and continued on as if nothing had changed.
Both computers got 183 units which should be completed in 3-4 hours and if there is no problems then I'll leave all my client.cfg files as read only and not have to worry about the file being corrupted.
Posted this same post on Stanford's request for bugs and requested changes also.
The file is read by the core program to get the information of client, team, and number of completed units. It then increases the completed units and rewrites the information back to disk.
In order to keep this from happening again I made the file a read only file on two different computers that were about to complete a wu. Both computers finished their wu and transmitted it, requested a new wu and gave the number of completed wu's and continued on as if nothing had changed.
Both computers got 183 units which should be completed in 3-4 hours and if there is no problems then I'll leave all my client.cfg files as read only and not have to worry about the file being corrupted.
Posted this same post on Stanford's request for bugs and requested changes also.