...can you add a red flag if the last line is something like this: "Folding@Home Client Shutdown."
By design, I'm not looking at the actual log file-- just the status file. Reason being, I know of no good way to start at the end of the log file and just look at the last few lines. I'd have to start parsing from the beginning of the rather lengthy file. With VBScript, especially, this is a slow, CPU-intensive process.
Instead, I just look at the file timestamp on the unitinfo.txt file (status file) and if the difference between that and now gets to be too long (beyond the number of minutes specified in the script), I flag the machine.
This should be sufficient. It's possible, though, that you've found a hole in that logic. Can you let me know which machine it is, the time it shut down, and when you discovered that it had? I'll compare those times to what's in the log file and see what went wrong.
Thanks!
[04:21:12] Folding@home Core Shutdown: CORE_OUTDATED [04:21:12] CoreStatus = 6E (110) [04:21:12] + Core out of date. Auto updating... [04:21:12] New core downloaded for this work unit, but still out of date. [04:21:12] Folding@Home will go to sleep for 1 day as there have been 5 consecutive Cores executed which failed to complete a work unit. [04:21:12] (To wake it up early, quit the application and restart it.) [04:21:12] If problems persist, please visit our website at http://folding.stanford.edu for help. [04:21:12] + Sleeping...
I'm noticing that the status file is still being written too-- and so my machines are not showing red, and they're all showing 100% from the previous project.
I think this might be your issue, FreeAtlanta. Was your frozen machine showing 100%?