stdout.txt cut off in CC 4.19

Message boards : Preferences : stdout.txt cut off in CC 4.19

Author Message
Profile Ananas
Send message
Joined: Mar 7 06
Posts: 58
Credit: 752,054
RAC: 408

BOINC 4.19 seems to have a too small read buffer for the stdout tag in sched_reply. Is that a problem for the beta test in any way?

Chris Sutton
Send message
Joined: Nov 10 05
Posts: 297
Credit: 4,941,683
RAC: 0

If you have a look at the results returned from the wu's, you'll notice that there's quite a large amount (+/- 16KB) of debug data returned. If BOINC 4.19 isn't able to to return all of this data, diagnosing any problems occuring on these clients will probably be impossible.

So I guess it's maybe not a problem if you are not concerned to know why a particular result is invalid, but I leave it to a project member to give a confirmed answer.

Profile Ananas
Send message
Joined: Mar 7 06
Posts: 58
Credit: 752,054
RAC: 408

So far I didn't have trouble, all results valid - and if I had a persistent problem, I could still catch stdout.txt before it gets added to client_state.xml I guess (NTFS hard link should help save the contents)

So it would only be a problem for single bad results.

Post to thread

Message boards : Preferences : stdout.txt cut off in CC 4.19


Return to malariacontrol.net main page


Copyright © 2013 africa@home