[pre][CRITICAL]: APP DEBUG: Application caught signal 15.[/pre]
The signal 15 is SIGTERM. This is a signal sent to the App from other processes. It may be someone issuing a kill command, or the BOINC client failing to shutdown the App more gracefully. It usually isn't something to worry about, as the client should be able to start the App again, and the App should simply continue from the checkpointed state, like it does in your results.
I rather think that your invalid results are some that sometimes occur with this App and the current setup. For the rest of the current S4 run there's not much we or you can do about that, apart from switching back to the "official" App, but the new S5 run setup should prevent this.
The signal 15 is SIGTERM. This is a signal sent to the App from other processes. It may be someone issuing a kill command, or the BOINC client failing to shutdown the App more gracefully. It usually isn't something to worry about, as the client should be able to start the App again, and the App should simply continue from the checkpointed state, like it does in your results.
The machine is rebooted fairly often, switching back and forth between OS 9 and X, which may have something to do with it, particularly in combination with my obsolete Menubar v5.2.13—I’ve been meaning to update my client to v5.4.9 but haven’t got around to it yet …
Quote:
I rather think that your invalid results are some that sometimes occur with this App and the current setup. For the rest of the current S4 run there's not much we or you can do about that, apart from switching back to the "official" App, but the new S5 run setup should prevent this.
OK, thanks. Is v4.67 likely to be any better in this regard? (I’m planning to try it out anyway.)
RE: [pre][CRITICAL]: APP
)
The signal 15 is SIGTERM. This is a signal sent to the App from other processes. It may be someone issuing a kill command, or the BOINC client failing to shutdown the App more gracefully. It usually isn't something to worry about, as the client should be able to start the App again, and the App should simply continue from the checkpointed state, like it does in your results.
I rather think that your invalid results are some that sometimes occur with this App and the current setup. For the rest of the current S4 run there's not much we or you can do about that, apart from switching back to the "official" App, but the new S5 run setup should prevent this.
BM
BM
Thanks for the updated 4.67
)
Thanks for the updated 4.67 app Bernd, your efforts are much appreciated!
RE: The signal 15 is
)
The machine is rebooted fairly often, switching back and forth between OS 9 and X, which may have something to do with it, particularly in combination with my obsolete Menubar v5.2.13—I’ve been meaning to update my client to v5.4.9 but haven’t got around to it yet …
OK, thanks. Is v4.67 likely to be any better in this regard? (I’m planning to try it out anyway.)
RE: OK, thanks. Is v4.67
)
No, probably not, i.e. not with the WUs remaining for the S4 analysis.
BM
BM