Bad executables can cause infinite loop

[charlief]

If a defective project application always exits with code 0, the BOINC Client will restart it forever and will never contact the server. The message window does show "If this happns repeatedly, you may need to reset the project" but many users may not notice this, and some won't follow the instructions even though they do see it.

Suggestion: If the Client detects this happening N times within M minutes, abort the task.

This happened with setiathome-5.21.powerpc-apple-darwin. All the associated files had the executable set, so the BOINC Client tried to execute the setiathome-5.21_AUTHORS file instead of the application.

At 2:21 PM -0700 7/19/07, Jeff Cobb wrote:

The underlying problem is that the executable name is different
than the directory name:

   setiathome_5.21_powerpc-apple-darwin/
               setiathome-5.21.powerpc-apple-darwin

When the name match fails, the boinc client may resort to using
the executable flag. 

So another possibility might be to create an error condition when there is no match, ideally at the server.

I'm not sure what directory Jeff means here, as the application file is in the "BOINC Data/projects/setiathome.berkeley.edu/" directory on my Mac; there is no directory with a name like the one Jeff mentions. Perhaps he is talking about a directory on the BOINC server, but it's unclear to me how that would affect the BOINC Client's choice of executables.

[Nicolas]

fix typo on description