Ah. My memory isn't failing after all. Mo's http://boinc.berkeley.edu/trac/ticket/985
----- Original Message ----- From: "Richard Haselgrove" <[email protected]> To: <[email protected]> Sent: Tuesday, May 25, 2010 9:20 PM Subject: Re: [boinc_dev] host punishment mechanism revisited > Part of the trouble here is that the BOINC message log (without special > logging flags) tends only to mention 'Output file absent'. It takes quite > sophisticated knowledge of BOINC to understand that 'Output file absent' > almost invariably means that the science application had previously > crashed. > I've written that repeatedly on project message boards (including BOINC's > own message board): I could have sworn I'd also written about it quite > recently on one of these BOINC mailing lists, but none of my search tools > is > turning up the reference. > > I think it would help if the BOINC client message log could actually use > the > word 'error', as in > > "Computation for task xxxxxxxxxxxxxxx finished with an error > "Exit status 3 (0x3) for task xxxxxxxxxxxxxxx" > > BoincView can log them - why not BOINC itself? _______________________________________________ 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.
